ANSI INCITS416-2006 Information technology - Fibre Channel Protocol for SCSI Third Version (FCP-3)《信息技术.SCSI的纤维信道协议.第3版(FCP-3)》.pdf

《ANSI INCITS416-2006 Information technology - Fibre Channel Protocol for SCSI Third Version (FCP-3)《信息技术.SCSI的纤维信道协议.第3版(FCP-3)》.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS416-2006 Information technology - Fibre Channel Protocol for SCSI Third Version (FCP-3)《信息技术.SCSI的纤维信道协议.第3版(FCP-3)》.pdf（145页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Fibre Channel Protocol for SCSI,Third Version (FCP-3)ANSI INCITS 416-2006ANSIINCITS416-2006Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted wi

2、thout license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSIINCITS 416-2006American National Standardfor Information Technology Fibre Channel Protocol for SCS

3、I,Third Version (FCP-3)SecretariatInformation Technology Industry CouncilApproved June 22, 2006American National Standards Institute, Inc.AbstractThis standard describes the frame format and protocol definitions required to transfer commands and databetween a SCSI (Small Computer System Interface) i

4、nitiator and target using the Fibre Channel family ofstandards. The second version (ANSI INCITS 350) added optional retransmission, task ordering, and con-firmation capabilities. This third version incorporates bi-directional commands, removes information thatis now contained in other standards, and

5、 describes additional error recovery capabilities for the FibreChannel Protocol.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Standard require

6、s review by ANSI that therequirements 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 in

7、terests. Substantial agreement 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; theirexisten

8、ce does not in any respect 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 circumstan

9、ces give an interpretation 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

10、 sponsor whose name appears 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. Pu

11、rchasers of American National 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 2006 by Information

12、 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, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The develo

13、pers of this standard 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

14、 this standard. 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 v

15、alidity of this 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

16、be obtained from 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.Copyright American Nat

17、ional Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without l

18、icense from IHS-,-,-ContentsPageForeword xIntroduction .xv1 Scope . 12 Normative references 12.1 Qualification and availability of references. 12.2 Published standard and technical report references 12.3 References under development . 12.4 Other references 23 Definitions, abbreviations and conventio

19、ns 23.1 Definitions 23.2 Abbreviations . 53.3 Keywords . 73.4 Editorial conventions 74 General . 94.1 Structure and concepts 94.2 FCP I/O operations 104.3 Bidirectional and unidirectional commands and FCP_RSP IU format . 124.4 Precise delivery of SCSI commands 124.5 Confirmed completion of FCP I/O o

20、perations 134.6 Retransmission of unsuccessfully transmitted IUs. 144.7 Task retry identification 144.8 Discovery of FCP capabilities 154.9 Task management . 154.10 Clearing effects of task management, FCP, FC-FS-2, FC-LS, and FC-AL-2 actions . 164.11 I_T nexus loss notification events 194.12 Transp

21、ort Reset notification events 194.13 Port Login/Logout. 194.14 Process Login and Process Logout . 204.15 Link management. 204.16 FCP addressing and Exchange identification 204.17 Use of World Wide Names. 20i5 FC-FS-2 frame header 215.1 FC-FS-2 frame header overview 21Copyright American National Stan

22、dards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHSPage5.2 FC-FS-2 frame header fields 215.2.1 r_ctl field 215.2.2 d_id field 215.2.3 cs_ctl field . 215.2.4 s_id field 215.2.5 type field 215.2.6 f_ctl field 225.2.7 se

23、q_id field 225.2.8 df_ctl field 225.2.9 seq_cnt field 225.2.10 ox_id field 225.2.11 rx_id field . 225.2.12 parameter field 226 FCP link service definitions . 236.1 Overview of link service requirements . 236.2 Overview of Process Login and Process Logout . 236.3 PRLI . 246.3.1 Use of PRLI by the Fib

24、re Channel Protocol 246.3.2 Process_Associator requirements 246.3.3 New or repeated Process Login 246.3.4 PRLI request FCP Service Parameter page format 246.3.5 PRLI accept FCP Service Parameter page format . 286.4 PRLO . 296.5 Read Exchange Concise (REC). 297 FC-4 specific Name Server registration

25、and objects . 307.1 Overview of FC-4 specific objects for the Fibre Channel Protocol. 307.2 FC-4 TYPEs object 307.3 FC-4 Features object . 308 FC-4 Link Service definitions 318.1 FC-4 Link Services for the Fibre Channel Protocol 318.2 Sequence Retransmission Request (SRR) 318.3 FCP FC-4 Link Service

26、 Reject (FCP_RJT) 339 FCP Information Unit (IU) usage and formats . 359.1 FCP Information Unit (IU) usage 359.2 FCP_CMND IU. 369.2.1 Overview and format of FCP_CMND IU . 369.2.2 FCP_CMND IU field descriptions 379.2.2.1 fcp_lun field 379.2.2.2 COMMAND REFERENCE NUMBER field 389.2.2.3 priority field .

27、 389.2.2.4 task attribute field . 389.2.2.5 TASK MANAGEMENT FLAGS FIELD 38ii9.2.2.6 additional fcp_cdb length field 40-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Page9.

28、2.2.7 rddata and wrdata bits 419.2.2.8 fcp_cdb field . 419.2.2.9 additional_fcp_cdb field 419.2.2.10 fcp_dl field 419.2.2.11 fcp_bidirectional_read_dl field 429.3 FCP_XFER_RDY IU 429.3.1 Overview and format of FCP_XFER_RDY IU . 429.3.2 fcp_data_ro field 439.3.3 fcp_burst_len field . 439.4 FCP_DATA I

29、U 439.4.1 FCP_DATA IU overview 439.4.2 FCP_DATA IUs for read and write operations . 449.4.3 FCP_DATA IUs for bidirectional commands . 449.4.4 FCP_DATA IU use of fill bytes 459.5 FCP_RSP IU 459.5.1 Overview and format of FCP_RSP IU . 459.5.2 retry delay timer field . 479.5.3 fcp_bidi_rsp bit 479.5.4

30、fcp_bidi_read_resid_under bit . 489.5.5 fcp_bidi_read_resid_over bit . 489.5.6 FCP_CONF_REQ BIT . 489.5.7 fcp_resid_under bit 489.5.8 fcp_resid_over bit 489.5.9 fcp_sns_len_valid bit . 489.5.10 fcp_rsp_len_valid bit 489.5.11 SCSI status code field . 499.5.12 fcp_resid field 499.5.13 fcp_bidirectiona

31、l_read_resid field 499.5.14 fcp_sns_len field 509.5.15 fcp_rsp_len field 509.5.16 fcp_rsp_info field . 509.5.17 fcp_sns_info field . 519.6 FCP_CONF IU . 5210 SCSI mode parameters for the Fibre Channel Protocol 5310.1 Overview of mode pages for the Fibre Channel Protocol. 5310.2 Disconnect-Reconnect

32、mode page 5310.2.1 Overview and format of Disconnect-Reconnect mode page for FCP 5310.2.2 buffer full ratio field 5410.2.3 buffer empty ratio field . 5510.2.4 bus inactivity limit field . 5510.2.5 disconnect time limit field 5510.2.6 connect time limit field . 5510.2.7 maximum burst size field . 551

33、0.2.8 emdp bit . 5610.2.9 FAA, FAB, FAC BITS 5610.2.10 first burst size field . 5610.3 Fibre Channel Logical Unit Control mode page 57iiiCopyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from

34、IHSPage10.4 Fibre Channel Port Control mode page . 5710.4.1 Overview and format of Fibre Channel Port Control mode page 5710.4.2 DISABLE TARGET ORIGINATED LOOP INITIALIZATION (DTOLI) bit . 5810.4.3 DISABLE TARGET INITIATED PORT ENABLE (DTIPE) bit 5810.4.4 ALLOW LOGIN WITHOUT LOOP INITIALIZATION (ALW

35、LI) bit 5810.4.5 REQUIRE HARD ADDRESS (RHA) bit . 5910.4.6 disable loop master (dlm) bit . 5910.4.7 DISABLE DISCOVERY (DDIS) bit . 5910.4.8 PREVENT LOOP PORT BYPASS (PLPB) bit 5910.4.9 DISABLE TARGET FABRIC DISCOVERY (DTFD) bit 5910.4.10 sequence initiative resource recovery timeout value (rr_tovseq

36、_init) field . 6011 Timers for FCP operation and recovery 6111.1 Summary of timers for the Fibre Channel Protocol 6111.2 Error_Detect Timeout (E_D_TOV). 6211.3 Resource Allocation Timeout (R_A_TOV) . 6211.4 Resource Recovery Timeout (RR_TOV) 6211.5 Read Exchange Concise Timeout Value (REC_TOV). 6211

37、.6 Upper Level Protocol Timeout (ULP_TOV) 6312 Link error detection and error recovery procedures 6412.1 Error detection and error recovery overview 6412.1.1 Exchange level 6412.1.2 Sequence level 6412.2 FCP error detection 6412.2.1 Overview of FCP-3 error detection 6412.2.2 FCP-3 error detection us

38、ing protocol errors for all classes of service . 6412.2.3 Error detection mechanisms for acknowledged classes of service . 6512.3 Exchange level recovery using recovery abort 6612.3.1 Recovery abort overview . 6612.3.2 Initiator FCP_Port invocation of recovery abort 6612.3.3 Target FCP_Port response

39、 to recovery abort . 6612.3.4 Additional error recovery by initiator FCP_Port . 6712.3.5 Additional error recovery by target FCP_Port . 6712.4 Sequence level error detection and recovery. 6712.4.1 Using information from REC to perform Sequence level recovery 6712.4.1.1 Polling Exchange state with RE

40、C . 6712.4.1.2 Detection of errors while polling with REC . 6812.4.1.3 FCP_CMND IU recovery 6812.4.1.4 FCP_XFER_RDY IU recovery . 6812.4.1.5 FCP_RSP IU recovery . 6812.4.1.6 FCP_DATA IU recovery - write operations 6912.4.1.7 FCP_DATA IU recovery - read operations . 7012.4.1.8 FCP_CONF IU recovery 70

41、12.4.2 Additional error recovery requirements . 7112.4.2.1 Error indicated in ACK 71iv12.4.2.2 Missing ACK . 71-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Page12.4.2.3

42、Distinguishing Exchange to be aborted 7112.5 Second-level error recovery . 7112.5.1 ABTS error recovery 7112.5.2 REC error recovery . 7212.5.3 SRR error recovery . 7212.6 Responses to FCP type frames before PLOGI or PRLI . 72AnnexesA FCP-3 mapping to SAM-3 (Fibre Channel Protocol Service mapping to

43、SCSI Architectural Model - 3 73A.1 Definition of procedure terms . 73B FCP Examples 75B.1 Examples of the use of FCP Information Units (IUs) . 75B.1.1 Overview of examples . 75B.1.2 SCSI FCP read operation . 75B.1.3 SCSI FCP write operation . 76B.1.4 SCSI FCP operation with no data transfer or with

44、check condition . 76B.1.5 SCSI FCP read operation with multiple FCP_DATA IUs 77B.1.6 SCSI FCP write operation with FCP_XFR_RDY disabled 77B.1.7 SCSI FCP bidirectional command with write before read . 78B.1.8 SCSI FCP bidirectional command with read before write . 78B.1.9 SCSI FCP bidirectional comma

45、nd, write first, write FCP_XFER_RDY disabled . 79B.1.10 SCSI FCP bidirectional command with intermixed writes and reads 80B.1.11 SCSI linked commands . 81B.1.12 SCSI WRITE command with confirmed completion 82B.1.13 SCSI FCP task management function 82B.2 FCP write example, frame level . 83B.3 FCP re

46、ad example, frame level . 85C Error detection and recovery action examples 87C.1 Introduction 87D FCP device discovery procedure 121D.1 FCP Device Discovery Procedure . 121D.1.1 Initiator discovery of Fabric-attached target FCP_Ports . 121D.1.2 Initiator discovery of loop-attached target FCP_Ports 1

47、21D.2 Fabric and Device Authentication 122D.3 Logical unit authentication . 122vCopyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-PageE FCP-3 examples of link service usage . 123E

48、.1 Formats for recovery link services . 123E.2 Abort Sequence (ABTS) Request 123E.2.1 Abort Sequence (ABTS) Request fields . 123E.2.2 Basic Accept (BA_ACC) Frame to ABTS . 124E.2.3 Basic Reject (BA_RJT) Frame to ABTS . 125E.3 Reinstate Recovery Qualifier (RRQ) 125E.3.1 RRQ request format 125Tables1 SCSI and Fibre Channel Protocol functions . 102 Discovery of FCP-3 capabilities 153 Task management functions, SAM-3 to FCP-3 164 Clearing effects of link related functions . 185 Clearing effects of initiator FCP_Port actions . 196 FCP frame header 217 FCP Service Parameter page, PRLI req