欢迎来到麦多课文档分享! | 帮助中心 海量文档,免费浏览,给你所需,享你所想!
麦多课文档分享
全部分类
  • 标准规范>
  • 教学课件>
  • 考试资料>
  • 办公文档>
  • 学术论文>
  • 行业资料>
  • 易语言源码>
  • ImageVerifierCode 换一换
    首页 麦多课文档分享 > 资源分类 > PDF文档下载
    分享到微信 分享到微博 分享到QQ空间

    ANSI INCITS 387-2004 for Information Technology Fibre Channel - Generic Services-4 (FC-GS-4).pdf

    • 资源ID:435687       资源大小:1.32MB        全文页数:365页
    • 资源格式: PDF        下载积分:10000积分
    快捷下载 游客一键下载
    账号登录下载
    微信登录下载
    二维码
    微信扫一扫登录
    下载资源需要10000积分(如需开发票,请勿充值!)
    邮箱/手机:
    温馨提示:
    如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
    如需开发票,请勿充值!如填写123,账号就是123,密码也是123。
    支付方式: 支付宝扫码支付    微信扫码支付   
    验证码:   换一换

    加入VIP,交流精品资源
     
    账号:
    密码:
    验证码:   换一换
      忘记密码?
        
    友情提示
    2、PDF文件下载后,可能会被浏览器默认打开,此种情况可以点击浏览器菜单,保存网页到桌面,就可以正常下载了。
    3、本站不支持迅雷下载,请使用电脑自带的IE浏览器,或者360浏览器、谷歌浏览器下载即可。
    4、本站资源下载后的文档和图纸-无水印,预览文档经过压缩,下载后原文更清晰。
    5、试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。

    ANSI INCITS 387-2004 for Information Technology Fibre Channel - Generic Services-4 (FC-GS-4).pdf

    1、American National StandardDeveloped byfor Information Technology Fibre Channel -Generic Services-4 (FC-GS-4)ANSI INCITS 387-2004ANSIINCITS387-2004ANSIINCITS 387-2004American National Standardfor Information Technology Fibre Channel -Generic Services-4 (FC-GS-4)SecretariatInformation Technology Indus

    2、try CouncilApproved August 3, 2004 American National Standards Institute, Inc.AbstractThis standard describes in detail the basic Fibre Channel services introduced in FC-FS. In addition, thisdocument describes any ancillary functions and services required to support the Fibre Channel services.Servic

    3、es described include name services, management services, discovery services, time services, andalias services. This standard adds additional services to, and replaces, ANSI INCITS 348-2001.Approval of an American National Standard requires review by ANSI that therequirements for due process, consens

    4、us, 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 interests. Substantial agreement means much more thana simple ma

    5、jority, 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; theirexistence does not in any respect preclude anyone, whether he has app

    6、rovedthe 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 circumstances give an interpretation of any American NationalStandard. M

    7、oreover, 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 sponsor whose name appears on the titlepage of this standard.

    8、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. Purchasers of American National Standards mayreceive current inf

    9、ormation 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 2004 by Information Technology Industry Council (ITI)All rights reserved.No part

    10、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 developers of this standard have requested that holders of patents t

    11、hat may berequired for the implementation of the standard 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

    12、following calls for the identification of patents that 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

    13、 are not required to avoid infringement in the use of this standard.iContentsPageForeword xxIntroduction xxv1 Scope . 12 Normative References 22.1 Overview . 22.2 Approved references . 22.3 References under development 22.4 Other references . 33 Definitions and conventions . 43.1 Overview . 43.2 Def

    14、initions . 43.3 Editorial Conventions 73.4 Abbreviations, acronyms and symbols 83.5 Keywords 94 Common Transport for Generic Services (CT) 104.1 Overview . 104.2 General concepts 114.3 CT information unit 124.3.1 Overview . 124.3.2 Basic CT_IU preamble description 134.3.3 Extended CT_IU preamble des

    15、cription . 184.3.4 Vendor Specific CT_IU Preamble . 194.3.5 CT_IU Additional information 214.4 CT Information Units (CT_IU) . 214.4.1 Overview . 214.4.2 Request CT_IU . 214.4.3 Accept CT_IU 214.4.4 Reject CT_IU . 214.5 FC-FS mapping . 234.5.1 Overview . 234.5.2 Synchronous mode transactions . 234.5.

    16、3 Asynchronous mode transactions . 264.6 Time constants 294.6.1 Overview . 294.6.2 Request to response time . 294.6.3 Database propagation delay . 294.7 Persistence of actions after Logout 30iiPage4.8 CT Authentication 304.8.1 Overview . 304.8.2 Secure Association Attributes . 314.8.3 Security Algor

    17、ithms . 324.9 Common Requests . 324.9.1 Description 324.9.2 CT_IU preamble values 324.9.3 Reason Code Explanations . 334.9.4 Get More Information (GMI) 334.9.5 Server Registration and State Change Notification Initiation 345 Directory Service 365.1 Overview . 365.2 Name Server . 365.2.1 Overview . 3

    18、65.2.2 Name Server protocol . 385.2.3 Name Server objects Formats . 435.2.4 Reason code explanations 515.2.5 Commands 536 Management service 956.1 Overview . 956.2 Fabric Configuration Server 976.2.1 Overview . 976.2.2 Protocol . 976.2.3 Fabric Configuration Server Objects and Attributes 1016.2.4 Re

    19、ason code explanations 1226.2.5 Commands 1246.3 Unzoned Name Server 1566.3.1 Overview . 1566.3.2 Protocol . 1566.3.3 Unzoned Name Server objects Formats 1586.3.4 Reason code explanations 1586.3.5 Commands 1586.4 Fabric Zone Server . 1596.4.1 Overview . 1596.4.2 Terminology 1616.4.3 Protocol . 1626.4

    20、.4 Zoning Management Framework 1626.4.5 Default Zoning . 1636.4.6 Basic Zoning Management . 1646.4.7 Enhanced Zoning Management 1676.4.8 Zoning Data Structures . 1726.4.9 Reason code explanations 1906.4.10 Zoning Management Commands 1926.5 Security Policy Server . 2416.5.1 Overview . 2416.5.2 Protoc

    21、ol . 241iiiPage6.6 Fabric Device Management Interface . 2426.6.1 Overview . 2426.6.2 FDMI Relationship to the Name Server . 2426.6.3 GS_Subtypes 2426.6.4 HBA Management Server . 2427 Alias Service . 2657.1 Overview . 2657.2 Alias Server . 2657.2.1 Overview . 2657.2.2 Protocol . 2657.2.3 Data Fields

    22、2737.2.4 Reason code explanations 2777.2.5 Commands 2788 Key Distribution Service 288AnnexesA Service Interface Provided by FC-CT 289A.1 Overview . 289A.2 FC-CT Session Services 290A.2.1 FC_CT_REG.request 290A.2.2 FC_CT_REG_STATUS.indication 291A.2.3 FC_CT_DEREG.request 292A.2.4 FC-CT_DEREG_STATUS.i

    23、ndication . 292A.3 FC-CT Transaction Services 293A.3.1 FC_CT_TRANSACTION.request 293A.3.2 FC_CT_TRANSACTION_TAG.indication . 294A.3.3 FC_CT_TRANSACTION.confirmation 294A.3.4 FC_CT_TRANSACTION.indication . 295B FC-4 Feature bits . 296B.1 Overview . 296B.2 FCP-2 296C Discovery 297C.1 Introduction . 29

    24、7C.2 Basic Assumptions . 297C.3 Definitions . 298C.3.1 Fabric 298C.3.2 Fabric_Name 298C.3.3 Fibre Channel Node 298C.3.4 Fibre Channel storage area network 298ivPageC.3.5 In-Band Management Identifier 298C.3.6 Logical name 298C.3.7 Management access point 298C.3.8 Management application 298C.3.9 Plat

    25、form device . 298C.3.10 Platform Name 299C.3.11 Interconnect Element Name . 299C.3.12 Fibre Channel WKAs 299C.4 Basic Fibre Channel SAN Structure . 299C.4.1 Overview . 299C.4.2 Physical Fibre Channel SAN Components . 300C.4.3 Logical Fibre Channel SAN Components . 300C.4.4 Relationships and Associat

    26、ions 301C.5 Fiber Channel SAN Topology Views 301C.5.1 Overview . 301C.5.2 End-to-End Logical View 301C.5.3 End-to-End Physical View 302C.5.4 Fabric View . 302C.5.5 SAN Component Attributes 303C.6 Discovery of the Fibre Channel SAN Topology 304C.6.1 Overview . 304C.6.2 Fibre Channel Generic Services

    27、. 304C.6.3 Management Service 307C.6.4 Additional Discovery Mechanisms 309C.7 Topology Discovery Steps 309C.8 Discovery of a Fibre Channel SANs Management Capabilities . 310C.8.1 Overview . 310C.8.2 Management Access Points . 310C.8.3 Management Access Point Handle 310C.8.4 Discovery of Management C

    28、apabilities Steps 311D Example of Zone Services 312D.1 Introduction . 312D.2 Example Zone Configuration 313D.3 Zone management subsytems . 314D.4 Fabric Zone Server as a Conduit 314vPageD.5 Accessing an Active Zone Set 315D.6 Fabric Zone Server Repository . 315E Time Service . 316E.1 Overview . 316E

    29、.2 Time Server 316E.2.1 Overview . 316E.2.2 Time Server protocol . 316E.2.3 Data formats . 317E.2.4 Reason code explanations 317E.2.5 Commands 318F Performance Server . 322F.1 Overview . 322F.2 Protocol . 322F.2.1 Overview . 322F.2.2 CT_IU preamble values 322F.2.3 Registration . 323F.2.4 Queries 323

    30、F.3 Performance Server Objects and Attributes 323F.3.1 Performance Instrumentation Objects . 323F.3.2 Performance Probe Object 325F.3.3 Performance Metrics Object 328F.4 Reason code explanations 330F.5 Commands 331F.5.1 Query Get Performance Server Payload Sizes (GPMPS) . 331F.5.2 Query Get Performa

    31、nce Probes (GPMP) . 332F.5.3 Set Performance Probe (SPMP) . 333F.5.4 Query Get Performance Metrics List (GPMML) . 334F.5.5 Query Get Performance Metrics (GPMM) 334F.5.6 Register Performance Metrics (RPMM) 335F.5.7 De-Register Performance Metrics (DPMM) . 335TablesTable 1 ISO and American Conventions

    32、. 7Table 2 CT_IU. 13Table 3 Basic CT_IU preamble. 13Table 4 GS_Type values. 14viPageTable 5 Options field bits 15Table 6 Options field bits 5-3 values. 16Table 7 Command/Response codes 17Table 8 Extended CT_IU preamble 18Table 9 Vendor Specific CT_IU preamble 19Table 10 Reject CT_IU Reason Codes 22T

    33、able 11 Reject CT_IU Reason Code explanations for all Servers . 23Table 12 CT_IU table for synchronous transaction 24Table 13 CT_IU table for asynchronous transactions 27Table 14 Secure Association Attributes . 31Table 15 Algorithm identifiers. 32Table 16 Common Request Command Codes 33Table 17 GMI

    34、Request CT_IU 34Table 18 SSB Request CT_IU . 34Table 19 SSE Request CT_IU . 35Table 20 Directory Service subtype values 36Table 21 Name Server Request types 37Table 22 Name Server Objects. 37Table 23 Name Server Request Command Codes. 38Table 24 FC4 TYPEs mapping 46Table 25 Port TYPE encoding. 48Tab

    35、le 26 FC4 Features mapping . 50Table 27 Reject CT_IU Reason code explanations . 51Table 28 GA_NXT Request CT_IU 53Table 29 Accept CT_IU to GA_NXT Request 55Table 30 GID_A Request CT_IU 56Table 31 Accept CT_IU to GID_A Request, Domain_ID Scope is zero. 56Table 33 GPN_ID Request CT_IU. 57Table 32 Acce

    36、pt CT_IU to GID_A Request, Domain_ID Scope is non-zero 57Table 34 Accept CT_IU to GPN_ID Request. 58Table 35 GNN_ID Request CT_IU. 58Table 36 Accept CT_IU to GNN_ID Request. 58Table 37 GCS_ID Request CT_IU. 59Table 38 Accept CT_IU to GCS_ID Request. 59Table 39 GFT_ID Request CT_IU 59viiPageTable 40

    37、Accept CT_IU to GFT_ID Request 60Table 41 GSPN_ID Request CT_IU. 60Table 42 Accept CT_IU to GSPN_ID Request. 60Table 43 GPT_ID Request CT_IU 61Table 44 Accept CT_IU to GPT_ID Request 61Table 45 GIPP_ID Request CT_IU 61Table 46 Accept CT_IU to GIPP_ID Request 62Table 47 GFPN_ID Request CT_IU . 62Tabl

    38、e 48 Accept CT_IU to GFPN_ID Request . 62Table 49 GHA_ID Request CT_IU . 63Table 50 Accept CT_IU to GHA_ID Request . 63Table 51 GFD_ID Request CT_IU . 63Table 52 Accept CT_IU to GFD_ID Request 64Table 53 GFF_ID Request CT_IU 64Table 54 Accept CT_IU to GFF_ID Request 65Table 55 GID_PN Request CT_IU .

    39、 65Table 56 Accept CT_IU to GID_PN Request . 65Table 57 GIPP_PN Request CT_IU . 66Table 58 Accept CT_IU to GIPP_PN Request . 66Table 59 GID_NN Request CT_IU . 66Table 60 Accept CT_IU to GID_NN Request . 67Table 61 GPN_NN Request CT_IU 67Table 62 Accept CT_IU to GPN_NN Request 68Table 63 GIP_NN Reque

    40、st CT_IU . 68Table 64 Accept CT_IU to GIP_NN Request . 69Table 65 GIPA_NN Request CT_IU. 69Table 66 Accept CT_IU to GIPA_NN Request. 69Table 67 GSNN_NN Request CT_IU . 69Table 68 Accept CT_IU to GSNN_NN Request . 70Table 69 GNN_IP Request CT_IU . 70Table 70 Accept CT_IU to GNN_IP Request . 70Table 7

    41、1 GIPA_IP Request CT_IU. 71Table 72 Accept CT_IU to GIPA_IP Request. 71Table 73 GID_FT Request CT_IU 72Table 74 Accept CT_IU to GID_FT Request 72viiiPageTable 75 GPN_FT Request CT_IU 73Table 76 Accept CT_IU to GPN_FT Request 74Table 77 GNN_FT Request CT_IU 75Table 78 Accept CT_IU to GNN_FT Request 7

    42、6Table 79 GID_PT Request CT_IU . 77Table 80 Accept CT_IU to GID_PT Request . 77Table 81 GID_IPP Request CT_IU 78Table 82 Accept CT_IU to GID_IPP Request 78Table 83 GPN_IPP Request CT_IU. 78Table 84 Accept CT_IU to GPN_IPP Request. 79Table 85 GID_FPN Request CT_IU. 79Table 86 Accept CT_IU to GID_FPN

    43、Request. 79Table 87 GPPN_ID Request CT_IU. 80Table 88 Accept CT_IU to GPPN_ID Request. 80Table 89 GID_FF Request CT_IU 81Table 90 Accept CT_IU to GID_FF Request 82Table 91 GID_DP Request CT_IU. 82Table 92 Accept CT_IU to GID_DP Request. 83Table 93 RPN_ID Request CT_IU . 83Table 94 RPN_ID Accept CT_I

    44、U 84Table 95 RNN_ID Request CT_IU. 84Table 96 RNN_ID Accept CT_IU . 84Table 97 RCS_ID Request CT_IU . 85Table 98 RCS_ID Accept CT_IU 85Table 99 RFT_ID Request CT_IU 86Table 100 RFT_ID Accept CT_IU 86Table 101 RSPN_ID Request CT_IU. 86Table 102 RSPN_ID Accept CT_IU . 87Table 103 RPT_ID Request CT_IU

    45、87Table 104 RPT_ID Accept CT_IU 87Table 105 RIPP_ID Request CT_IU) . 88Table 106 RIPP_ID Accept CT_IU. 88Table 107 RHA_ID Request CT_IU . 89Table 108 RHA_ID Accept CT_IU 89Table 109 RFD_ID Request CT_IU . 90ixPageTable 110 RFD_ID Accept CT_IU 90Table 111 RFF_ID Request CT_IU 91Table 112 RFF_ID Accep

    46、t CT_IU 91Table 113 RIP_NN Request CT_IU) 92Table 114 RIP_NN Accept CT_IU 92Table 115 RIPA_NN Request CT_IU . 92Table 116 RIPA_NN Accept CT_IU . 93Table 117 RSNN_NN Request CT_IU . 93Table 118 RSNN_NN Accept CT_IU 93Table 119 DA_ID Request CT_IU 94Table 120 DA_ID Accept CT_IU 94Table 121 Management

    47、Service subtype values . 95Table 122 Fabric Configuration Server Request Command Codes 98Table 123 Interconnect Element Type encoding 103Table 124 Logical Name Format 104Table 125 Management Address Format. 104Table 126 Information List Format . 105Table 127 Port Type encoding . 106Table 128 Port TX Type encoding 106Table 129 Port Module Type encoding 107Table 130 Physical Port Number Format . 108Table 131 Attached Port Name Format 108Table 132 Port Flags field bits 108Table 133 Port State encoding. 109Table 134


    注意事项

    本文(ANSI INCITS 387-2004 for Information Technology Fibre Channel - Generic Services-4 (FC-GS-4).pdf)为本站会员(tireattitude366)主动上传,麦多课文档分享仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文档分享(点击联系客服),我们立即给予删除!




    关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

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

    收起
    展开