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

加入VIP,免费下载
 

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

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

下载须知

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

版权提示 | 免责声明

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

ANSI INCITS 418-2006 For Information Technology C Fibre Channel C Switch Fabric- 4 (FC-SW-4).pdf

1、American National StandardDeveloped byfor Information Technology Fibre Channel Switch Fabric- 4(FC-SW-4)ANSI INCITS 418-2006ANSIINCITS418-2006ANSIINCITS 418-2006American National Standardfor Information Technology Fibre Channel Switch Fabric - 4 (FC-SW-4)SecretariatInformation Technology Industry Co

2、uncilApproved December 8, 2006 American National Standards Institute, Inc.AbstractThis standard describes the requirements for an interconnecting Fabric consisting of multiple FabricSwitch elements to support the ANSI/INCITS Fibre Channel - Framing and Signaling (FC-FS) and ANSI/INCITS Fibre Channel

3、 - Physical Interface (FC-PI) standards.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, in the judgement of the ANSI Board ofStand

4、ards 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 that a concerted effort be madetowards thei

5、r 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 procedures not conforming to the standards.The

6、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 Standard in the name of the AmericanNational S

7、tandards 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 the American National StandardsInstitute re

8、quire 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 StandardPublished byAmerican National Stan

9、dards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2006 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, 1250 Eye St

10、reet NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher ha

11、ve 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 following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No furth

12、er patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.iContentsPageForeword .xixIntroduction . xxvi1 Scope . 12 Normative references .

13、12.1 Approved references 22.2 References under development . 23 Definitions and conventions . 33.1 Definitions 33.2 Editorial conventions 83.3 State Machine notation 93.4 Abbreviations, acronyms, and symbols . 103.5 Definition of Compliance Terms . 103.6 Keywords . 113.7 T10 Vendor ID Fields . 124 S

14、tructure and Concepts . 134.1 Overview 134.2 E_Port Operation . 134.3 Fabric Operation 134.4 Fabric Definition . 144.5 Switch 144.6 Switching characteristics 174.6.1 Switching overview 174.6.2 Synchronous switching 174.6.3 Asynchronous switching 174.7 Switch Ports and Bridge Ports . 174.7.1 General

15、Characteristics . 174.7.2 F_Port 184.7.3 FL_Port 184.7.4 E_Port 184.7.4 B_Port 184.7.5 G_Ports and GL_Ports . 184.8 Fabric Addressing 194.9 Class F Service 215 Switch Ports and Bridge Ports . 225.1 Overview 225.2 Model elements 225.2.1 FC Transports 22iiPage5.2.2 Switch Transport 225.2.3 Control Fac

16、ilities 225.2.4 Link Services . 235.3 F_Port Operation . 235.4 FL_Port Operation . 245.5 E_Port Operation . 255.6 B_Port Operation . 275.7 Inter-Switch Link Behavior . 285.8 Class F Service 295.8.1 Class F Function 295.8.2 Class F Rules 295.8.3 Class F Frame Format . 315.8.4 Class F Flow Control . 3

17、26 Internal Link Services . 336.1 Switch Fabric Internal Link Services (SW_ILS) . 336.1.1 SW_ILS Overview 336.1.2 Switch Fabric Internal Link Service Accept (SW_ACC) . 356.1.3 Switch Fabric Internal Link Service Reject (SW_RJT) . 356.1.4 Exchange Link Parameters (ELP) . 396.1.4.1 ELP Request . 396.1

18、.4.2 R_RDY Flow Control 456.1.4.3 VC_RDY Flow Control 466.1.4.4 ELP Reply . 476.1.5 Exchange Fabric Parameters (EFP) 486.1.6 Domain Identifier Assigned (DIA) 526.1.7 Request Domain_ID (RDI) . 536.1.8 Hello (HLO) 566.1.8.1 HLO Overview 566.1.8.2 FSPF Header Format . 576.1.9 Link State Update (LSU) 58

19、6.1.9.1 LSU Overview . 586.1.9.2 Link State Record (LSR) Format 596.1.9.3 Link State Header Format . 606.1.9.4 Link Descriptor Format . 616.1.10 Link State Acknowledgement (LSA) 626.1.11 Build Fabric (BF) 626.1.12 Reconfigure Fabric (RCF) 636.1.13 Inter-Switch Registered State Change Notification (S

20、W_RSCN) 656.1.14 Distribute Registered Link Incident Records (DRLIR) . 676.1.15 Disconnect Class 1 Connection (DSCN) . 686.1.16 Merge Request (MR) . 696.1.16.1 Merge Request Payload . 706.1.16.1.1 Merge Request Payload in Basic Zoning 716.1.16.1.2 Merge Request Payload in Enhanced Zoning 726.1.16.2

21、Merge Request Reply . 736.1.17 Acquire Change Authorization Request (ACA) 746.1.18 Release Change Authorization (RCA) Request . 766.1.19 Stage Fabric Configuration Update (SFC) Request 77iiiPage6.1.19.1 SFC in Basic Zoning . 796.1.19.2 SFC in Enhanced Zoning 796.1.19.2.1 Operation Request Activate Z

22、one Set Enhanced 806.1.19.2.2 Operation Request Deactivate Zone Set Enhanced 806.1.19.2.3 Operation Request Distribute Zone Set Database 806.1.19.2.4 Operation Request Activate Zone Set by Name 816.1.19.2.5 Operation Request Set Zoning Policies . 816.1.20 Update Fabric Configuration (UFC) Request .

23、826.1.21 Check E_Port Connectivity (CEC) . 836.1.22 Exchange Switch Capabilities 856.1.23 Exchange Switch Support (ESS) . 886.1.23.1 ESS Request Payload . 896.1.23.2 Interconnect Element Information Object 896.1.23.3 Capability Object . 906.1.23.4 Service Specific Capability Formats 906.1.23.4.1 Dir

24、ectory Server Capability . 906.1.23.4.2 Fabric Controller Capability . 916.1.23.4.3 ESS Fabric Configuration Server Capability Object 916.1.23.4.4 ESS Enhanced Zone Server Capability Object . 926.1.23.4.5 Security Policy Server Capability Object . 936.1.23.4.6 ESS-Vendor Specific Capability Object 9

25、46.1.23.4.7 Domain Controller Capability Object . 956.1.23.4.8 Event Server Capability . 966.1.23.5 ESS Accept Payload . 966.1.24 Merge Request Resource Allocation (MRRA) 966.1.25 Switch Trace Route (STR) . 986.1.25.1 Basic Function . 986.1.26 Exchange Virtual Fabrics Parameters (EVFP) . 1046.1.26.1

26、 Basic Function . 1046.1.26.2 EVFP_SYNC Message Payload . 1076.1.26.2.1 Overview . 1076.1.26.2.2 Tagging Administrative Status Descriptor . 1086.1.26.2.3 Port VF_ID Descriptor . 1096.1.26.2.4 Locally-Enabled VF_ID List Descriptor . 1096.1.26.2.5 Vendor Specific Descriptor 1106.1.26.3 EVFP_COMMIT Mes

27、sage Payload . 1106.1.27 Enhanced Acquire Change Authorization Request (EACA) . 1106.1.27.1 Commit Exchange Preamble 1116.1.27.1.1 Transaction Identifier . 1116.1.27.1.2 Number of Switch Identifiers . 1126.1.27.1.3 Flags . 1136.1.27.1.4 ECS Switch List . 1136.1.28 Enhanced Stage Fabric Configuration

28、 (ESFC) Request 1146.1.29 Enhanced Update Fabric Configuration (EUFC) Request . 1156.1.30 Enhanced Release Change Authorization (ERCA) Request . 1166.1.31 Transfer Commit Ownership (TCO) Request . 1177 Fabric Configuration . 1197.1 Fabric Configuration Summary 1197.2 Switch Port Initialization . 120

29、7.2.1 Basic Operation 120ivPage7.2.2 Switch_Name Usage . 1297.2.3 Exchange Switch Capabilities Processing . 1297.2.4 B_Port Impact on ESC Processing 1307.2.5 Extensions to Support Virtual Fabrics 1307.3 Principal Switch Selection 1307.4 Address Distribution . 1377.4.1 Address Distribution Overview .

30、 1377.4.2 Domain_ID Distribution by the Principal Switch . 1397.4.3 Domain_ID Requests by the Switches 1417.5 E_Port and Fabric Isolation . 1447.6 B_Port Operation . 1457.6.1 Differences Between E_Ports and B_Ports . 1457.6.2 B_Port Internal Link Services 1457.6.3 B_Port Initialization 1467.6.4 Exam

31、ple B_Port Configuration 1478 Fabric Shortest Path First (FSPF) 1488.1 Overview 1488.1.1 Basic Components . 1488.1.2 Fabric connectivity . 1488.1.3 Addressing . 1488.1.4 Path Selection and Routing . 1498.1.5 FSPF Path Selection Summary . 1498.2 FSPF Message Processing . 1498.2.1 Message transmission

32、 . 1498.2.2 Message Reception and Tests 1508.3 Hello Protocol 1508.3.1 Basic Functions . 1508.3.2 Hello Message Transmission . 1508.3.3 Hello Message Parameters . 1508.3.4 Hello Message Reception 1518.4 The Link State Database . 1518.5 Usage of LSR Fields 1528.5.1 LSR Age 1528.5.2 LSR Incarnation Nu

33、mber . 1538.5.3 LSR Instance Rules . 1538.5.4 LSR Checksum 1548.5.5 Link Cost 1568.6 Link State Database Synchronization 1568.6.1 Synchronization Overview . 1568.6.2 Neighborhood and Adjacency 1578.6.3 Continuous Link State Database Synchronization . 1588.6.4 Reliable Flooding . 1598.6.4.1 Basic Ope

34、ration 1598.6.4.2 The Flooding Procedure . 1598.6.4.3 Generating a New LSR . 1598.6.4.4 Transmitting an LSR . 160vPage8.6.4.5 Receiving an LSR . 1608.7 Neighbor Finite State Machine (FSM) 1619 Distributed Services 1669.1 Basic Model 1669.2 Distributed Services Framework 1669.2.1 Goals and Characteri

35、stics of the Distributed Services Framework . 1669.2.2 Distributed Service Transport . 1669.2.2.1 Required FC-2 Parameters . 1669.2.2.2 FC-CT Header Usage . 1679.2.2.3 Frame Distribution . 1679.2.2.4 Domain Controller Service Parameters . 1679.2.3 Common Characteristics 1689.2.4 Zoning Consideration

36、s . 1689.2.5 Work Categories 1689.2.6 Frame Formats . 1699.2.7 FC-CT Command Restrictions . 1699.3 Distributed Name Server 1709.3.1 General Behavior . 1709.3.2 FC-CT for Distributed Name Servers . 1719.3.2.1 dNS Command Codes 1719.3.2.2 FC-CT Header usage for dNS . 1749.3.3 Name Server Objects . 175

37、9.3.4 FC-CT requests for dNS 1779.3.4.1 Get Entry based on Port Identifier . 1779.3.4.2 Get Entry based on Port_Name 1779.3.4.3 Get Entries based on Node_Name . 1789.3.4.4 Get Entries based on IP address (Node) 1799.3.4.5 Get Entries based on FC-4 TYPEs . 1799.3.4.6 Get Entries based on Port Type 18

38、09.3.4.7 Get Entries based on Zone Member . 1819.3.4.8 Get Entries based on Zone Name . 1829.3.4.9 Get Entries based on Port IP Address 1839.3.4.10 Get Entries based on FC-4 Features 1839.3.4.11 Get Entries based on Fabric Port_Name 1849.4 Distributed Management Server 1859.4.1 General Behavior . 18

39、59.4.2 FC-CT Header 1859.4.2.1 FC-CT Header Parameters . 1859.4.2.2 FC-CT Header Rule for Fabric Internal Requests . 1869.4.3 Fabric Configuration Service 1869.4.4 Unzoned Name Service . 1899.4.5 Fabric Zone Service . 1899.4.6 Fabric-Device Management Service 1899.4.6.1 Operational Characteristics o

40、f the FDMI Server . 1899.4.6.2 Registration Scenarios 1909.4.6.2.1 HBA Attached to a Single Switch 1909.4.6.2.2 HBA Attached to Multiple Switches . 1909.4.6.2.3 Resolution of the Principal HBA Manager . 190viPage9.4.6.3 FDMI Inter-Switch Messages 1919.4.6.3.1 General Format . 1919.4.6.3.2 FC-CT Head

41、er 1919.4.6.3.3 FDMI Header 1919.4.6.3.4 Payload . 1929.4.6.4 FDMI Inter-Switch Requests . 1929.4.6.5 FDMI Inter-Switch Responses 1939.4.6.5.1 Reject Response 1939.4.6.5.2 Accept Response 1939.4.6.6 FDMI Inter-Switch Operations 1939.4.6.6.1 Registration Notification (FRN) Operation 1939.4.6.6.2 De-R

42、egister Notification (FDRN) Operation 1949.4.6.6.3 Update Notification (FUN) Operation 1949.4.6.6.4 Update Forward (FUF) Operation . 1949.4.6.6.5 De-Register Forward (FDRF) Operation . 1949.4.6.6.6 Fetch . 1949.4.6.7 GS Client Initiated FDMI Requests . 1959.4.7 Other Fabric Internal Services . 1969.

43、4.7.1 Fabric Internal Requests . 1969.4.7.2 Get Management Server Capabilities (GCAP) Operation 1979.4.7.2.1 Capability Entry . 1979.4.7.2.2 Subtype Capability Bit Masks . 1989.5 Distributed Event Server 1989.5.1 General Behavior . 1989.5.2 FC-CT for Distributed Event Server . 1989.5.2.1 FC-CT Heade

44、r Parameters . 1989.5.2.2 dES Command Codes 19910 Switch Zone Exchange Annex D is normative and is considered part of thethe standard.Requests for interpretation, suggestions for improvements or addenda, or defect re-ports are welcome. They should be sent to the INCITS Secretariat, Information Tech-

45、nology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922.This standard was processed and approved for submittal to ANSI by the InternationalCommittee for Information Technology Standards (INCITS). Committee approval ofthe standard does not necessarily imply that all committ

46、ee members voted for its ap-proval. At the time it approved this standard, INCITS had the following members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAIM Global Dan MullenCharles Biss (Alt.)Apple Computer, Inc. David MichaelElectronic Industrie

47、s Alliance Edward Mikoski, Jr.David Thompson (Alt.)EMC Corporation Gary RobinsonFarance, Inc Frank FaranceTimothy Schoechle (Alt.)GS1 US Frank SharkeyJames Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Company. Karen HigginbottomSteve Mills (Alt.)Scott Jameson (Alt.)IBM Corporation . Ronald F.

48、SillettiPeter Schirling (Alt.)IEEE . Judith GormanTerry DeCourcelle (Alt.)Robert Pritchard (Alt.)Jodi Haasz (Alt.)Bob Labelle (Alt.)Intel. Philip WennblomDave Thewlis (Alt.)Jesse Walker (Alt.)Grace Wei (Alt.)Lexmark International . Don WrightDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft Corporation

49、 . Jim HughesDon Stanwyck (Alt.)Mike Ksar (Alt.)Isabelle Valet-Harper (Alt.)National Institute of Standards & Technology Michael HoganElaine Baker (Alt.)Dan Benigni (Alt.)xxOrganization Represented Name of RepresentativeOracle Corporation . Donald R. DeutschJim Melton (Alt.)Connie Myers (Alt.)Tony DiCenzo (Alt.)Toshihiro

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