ImageVerifierCode 换一换
格式:PDF , 页数:153 ,大小:942.40KB ,
资源ID:435648      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-435648.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(ANSI INCITS 350-2003 Information Technology - Fibre Channel Protocol for SCSI Second Version (FCP-2).pdf)为本站会员(fatcommittee260)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

ANSI INCITS 350-2003 Information Technology - Fibre Channel Protocol for SCSI Second Version (FCP-2).pdf

1、ANSI INCITS 350-2003for Information Technology Fibre Channel Protocol for SCSI, Second Version (FCP-2)ANSIINCITS 350-2003ANSIINCITS 350-2003American National Standardfor Information Technology Fibre Channel Protocol for SCSI,Second Version (FCP-2)SecretariatInformation Technology Industry CouncilApp

2、roved April 7, 2003American 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) initiator and target using the Fibre Channel family ofstandards. The second v

3、ersion adds optional retransmission, task ordering, and confirmation capabilities.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 standards developer.Consensus is established when,

4、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 that allviews and objections be considered, and t

5、hat 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, purchasing, or usingproducts, processes, or proce

6、dures 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 aninterpretation of an American National Stan

7、dard 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 revised orwithdrawn at any time. The procedures of t

8、he 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 AmericanNational Standards Institute.American National

9、StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2003 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 pr

10、ior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers 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

11、, nei-ther the developers nor the publisher have undertaken a patent search in order to identify which, ifany, patents may apply to 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 stand

12、ard,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 claim or of any rights in connection therewith. The knownpatent holder(s) has (have), however, filed a statement of willingness to grant a license undert

13、hese rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to ob-tain such a license. Details may 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

14、 implied that this is the only license that may be required to avoid infringement in the use ofthis standard.iContentsForeword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viIntroduction . . . . . . . . . . . .

15、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Normative references . . . . . . . . . . . .

16、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Qualification and availability of references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Published standard references . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17、 . . . . . . . . . . . . . . . . . 12.3 References under development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4 Other references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Defini

18、tions, abbreviations and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2 Abbreviations . . . . . . . . . . . . . .

19、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.3 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.4 Editorial conventions . . . . . . . . . . . . . . . . . . . . . . . .

20、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.1 Structure and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21、 . . . . . . . . . . . . . . . 94.2 Device management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.3 Precise delivery of SCSI commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.4 Confirmed complet

22、ion of FCP I/O Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.5 Retransmission of unsuccessfully transmitted data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.6 Task retry identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23、 . . . . . . . . . . . . . . . . . 144.7 Discovery of FCP capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.8 Task management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.9 Clear

24、ing effects of task management, FCP, FC-FS, and FC-AL-2 actions. . . . . . . . . . . 164.10 I_T nexus loss notification events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.11 Transport Reset notification events. . . . . . . . . . . . . . . . . . . . . . . . .

25、 . . . . . . . . . . . . . . . 194.12 Port login/logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.13 Process login/logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.14

26、 Link management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Fibre Channel protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.1 FCP addressing and Exchange identification

27、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.2 SCSI third-party device identifier for the Fibre Channel protocol . . . . . . . . . . . . . . . . . . 215.3 Use of World Wide Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

28、5.4 FCP Information Units (IUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.5 Fibre Channel protocol standard formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.6 FC-FS mappings to SCSI-3 functionality . . . . . . .

29、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.6.1 FC-FS frame header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.6.2 Frame header fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

30、. . . 245.6.2.1 R_CTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.6.2.2 D_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.6.2.3 CS_CTL . . . . . . . . . . . . .

31、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.6.2.4 S_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.6.2.5 TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32、. . . . . . . . . . . . . . . . 245.6.2.6 F_CTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.6.2.7 SEQ_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.6.2.8 DF_CTL

33、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.6.2.9 SEQ_CNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.6.2.10 OX_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . .

34、 . . . . . . . . . . . . . . . . . . . . . . . . . . 255.6.2.11 RX_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25ii6 FCP basic and extended link service definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35、276.1 Overview of link service requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276.2 Overview of Process Login/Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276.3 Process Login (PRLI) . . . . . . . . . . . . . . . .

36、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.3.1 Use of Process Login by the Fibre Channel protocol . . . . . . . . . . . . . . . . . . . . . . . 286.3.2 Process_Associator requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.3.3 New

37、 or repeated PRLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.3.4 Process Login request FCP Service Parameter page format . . . . . . . . . . . . . . . . 296.3.5 Process Login accept FCP Service Parameter page format . . . . . . . . . . . . . . . .

38、 . 326.4 Process Logout (PRLO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.5 Read Exchange Concise (REC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 FC-4 specific name server objects . . . . . . .

39、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357.1 Overview of FC-4 specific objects for the Fibre Channel protocol . . . . . . . . . . . . . . . . . 357.2 FC-4 Features object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

40、 . . . . 357.3 FC-4 Descriptor object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 FC-4 Link Service definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378.1 FC-4 Link Services for t

41、he Fibre Channel protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378.2 Sequence Retransmission Request (SRR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378.3 FCP FC-4 Link Service Reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42、. . . . . . . . . . 399 FCP Information Unit (IU) formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.1 FCP_CMND IU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.1.1 FCP_CMND IU fo

43、rmat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.1.2 FCP_CMND IU Field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.1.2.1 FCP_LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

44、. . . . . . . . . . . . . . . . . 419.1.2.2 COMMAND REFERENCE NUMBER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.1.2.3 task attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.1.2.4 TASK MANAGEMENT FLAGS .

45、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.1.3 Additional mechanisms for performing task management functions - ABORT TASK 469.2 FCP_XFER_RDY IU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469.2.1 Over

46、view and format of FCP_XFER_RDY IU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469.2.2 fcp_data_ro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479.2.3 fcp_burst_len . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47、 . . . . . . . . . . . . . . . . . . . . . . . 479.3 FCP_DATA IU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479.4 FCP_RSP IU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48、. . . . . 489.4.1 Overview and format of FCP_RSP IU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489.4.2 FCP_CONF_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499.4.3 fcp_resid_under . . . . . . . . . . . . . . . .

49、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509.4.4 fcp_resid_over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509.4.5 fcp_sns_len_valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509.4.6 fcp_rsp_len_valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509.4.7 SCSI status code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509.4.8 fcp_resid .

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1