Simplified Configuration and Management

Transcription

1 1 2 3 Copies of this document may be purchased from: INCITS xxx-200x Global Engineering, 15 Inverness Way East,T11/Project 1824-DT/Rev 1.1 Englewood, CO Phone: (800) or (303) Fax: (303) T11/10-367v0 4 5 FIBRE CHANNEL Simplified Configuration and Management (FC-SCM) REV 1.1 INCITS working draft proposed Technical Report04 August 2010 Secretariat: Information Technology Industry Council NOTE: This is a working draft Technical Report of Accredited Standards Committee INCITS. As such this is not a completed Technical Report. The T11 Technical Committee or anyone else may modify this document as a result of comments received anytime, or during a future public review and its eventual approval as a Technical Report. Use of the information contained herein is at your own risk. Permission is granted to members of INCITS, its technical committees, and their associated task groups to reproduce this document for the purposes of INCITS standardization activities without further permission, provided this notice is included. All other rights are reserved. Any duplication of this document for commercial or for-profit use is strictly prohibited. POINTS OF CONTACT: Steve Wilson(T11 Chair) Claudio Desanti (T11 Vice Chair) Craig W. Carlson (T11.3 Chair) Brocade Communications Cisco Systems, Inc. QLogic Corporation 1745 Technology Drive 170 W. Tasman Dr Bury Drive San Jose, CA San Jose, CA Eden Prairie, MN Voice: Voice: Voice: Fax: Fax: Fax: swilson@brocade.com cds@cisco.com craig.carlson@qlogic.com Claudio Desanti (Facilitator) William Martin (Editor) Cisco Systems, Inc. Emulex 170 W. Tasman Dr. 532 Gibson Dr. Suite 100 San Jose, CA Roseville, CA Voice: Voice: Fax: bill.martin@emulex.com cds@cisco.com

2 Summary of Comments on FC-SCM Page: 1 Number: 1 Author: SCM editor Subject: Sticky Note Date: 10/18/ :46:24 AM Comment format Number:E/T:ARWO:comment text:commenter suggested resolution, if any**resolution: Comment Summary Total comments: 117 Editorial Comments: 84 Technical Comments: 33 Total Resolved comments: 0 Resolved Editorial comments: 0 Resolved Technical comments: 0 Total Accepted comments: 0 Accepted Editorial comments: 0 Accepted Technical comments: 0 Total Rejected comments: 0 Rejected Editorial comments: 0 Rejected Technical comments: 0 Number: 2 Author: Avago Subject: Sticky Note Date: 9/24/ :07:21 AM avago-001:e::avago does not have a technical position on FC-SCM because it does not have products or technologies that bear on the topic. Number: 3 Author: EMC Subject: Sticky Note Date: 9/24/ :08:24 AM EMC-001:T::Will change vote to yes as soon as the target driven zoning functionality has been added. Number: 4 Author: NetApp Subject: Sticky Note Date: 9/24/ :10:04 AM Netapp-001:T::This TR is of limited use without TDZ. While TDZ mostly impacts other T11 Standards, it will need discussion in SCM (either this version, or SCM V2). Since there is no interest in a V2, then it must go here. Number: 5 Author: HP Subject: Sticky Note HP-001:T:: Date: 9/24/ :14:38 AM HP considers this technical-report as falling short of objectives and does not offer strong support. The positive impact to other standards is the best result of this technicalreport. Key Factors in favor of registered vote: 1. No big advantage for the SAN administrator as claimed, except zoning configuration everything else still needs to be done by a SAN trained administrator 2. New requirements (features) on Initiators, Fabric and Targets 3. Targets are more of a concern than the other two, although the max complexity is in the switch 4. Would need to make sure Storage is compliant to this spec extra development work for all our storage arrays a. Need to make sure all the FC registrations performed as defined b. Need to establish Session Begin and Session End protocols c. Strictly follow RSCN rules, etc 5. Likely to lead to two sets of qualification requirements (increased costs), or maybe three, only SCM devices, only non-scm devices or possibly a mix of both, and potentially new interoperability issues There are many ties and references to new features that are being added to other standards (FC-GS, FC-SW, FC-FCP and FC-LS). HP encourages these supporting standards being updated (some as recently as this July/August). Further, several of the requirements/new-features; such as the Initiator Name Server Sessions, the restrictions on RSCN delivery, the requirements for Port Fencing, etc.; would make for a more robust environment; as these new requirements put restrictions in place to curb behaviors that have proven problematic in the past. HP agrees that there are features that would simplify the SAN configuration for a "part-time person who is not skilled in IT management"; particularly the Wildcard zone concept and the required registrations and responses defined for the initiator ports, target ports and switch ports. The Wildcard zone population would all be done via device drivers and FW, offloading the need for the part-time/inexperienced person to do this. The registrations/responses that are defined would/could put much useful information at the fingertips of the person monitoring the SAN. Also, the Table 11 accumulated data would give a part-time IT manager some excellent information to hand off through an escalation process. While the changes might make the monitoring (not management) of the SAN a bit easier, Hp believes that the proposed implementation would fall far short of its stated goal of being able to "provide a SAN environment that can be managed by one part-time person who is not skilled in IT management." This technical report presumes that changes in Comments from page 1 continued on next page

3 Copies of this document may be purchased from: INCITS xxx-200x Global Engineering, 15 Inverness Way East,T11/Project 1824-DT/Rev 1.1 Englewood, CO Phone: (800) or (303) Fax: (303) T11/10-367v0 6 7 FIBRE CHANNEL Simplified Configuration and Management (FC-SCM) REV 1.1 INCITS working draft proposed 8 Technical Report04 August 2010 Secretariat: Information Technology Industry Council NOTE: This is a working draft Technical Report of Accredited Standards Committee INCITS. As such this is not a completed Technical Report. The T11 Technical Committee or anyone else may modify this document as a result of comments received anytime, or during a future public review and its eventual approval as a Technical Report. Use of the information contained herein is at your own risk. Permission is granted to members of INCITS, its technical committees, and their associated task groups to reproduce this document for the purposes of INCITS standardization activities without further permission, provided this notice is included. All other rights are reserved. Any duplication of this document for commercial or for-profit use is strictly prohibited. POINTS OF CONTACT: Steve Wilson(T11 Chair) Claudio Desanti (T11 Vice Chair) Craig W. Carlson (T11.3 Chair) Brocade Communications Cisco Systems, Inc. QLogic Corporation Technology Drive 170 W. Tasman Dr Bury Drive 11 San Jose, CA San Jose, CA Eden Prairie, MN Voice: Voice: Voice: Fax: Fax: Fax: swilson@brocade.com cds@cisco.com craig.carlson@qlogic.com Claudio Desanti (Facilitator) William Martin (Editor) Cisco Systems, Inc. Emulex 170 W. Tasman Dr. 532 Gibson Dr. Suite 100 San Jose, CA Roseville, CA Voice: Voice: Fax: bill.martin@emulex.com cds@cisco.com

4 the SAN configuration are performed by a single management tool. One gets a sense from reading this document, that the management functions would be performed via the HBA API as defined in FC-HBA, which is limited in its capabilities. It would not provide the capabilities to set up cu/ldev, LUN and host mappings on an array; or set up disk groups and create LUNS on an hp storage array. This activity would still require a knowledgeable person. There might be some level of management possible from this tool, but it would not be able to manage everything. The reports usage of the term 'manage' is not well defined and bounded. Number: 6 Author: HP Subject: Sticky Note Date: 9/24/ :16:51 AM HP-002:T::Referring to the Name Sever queries (ex. GPN_SDFCP) in the Target Port State Machine (ex. States T8 and/or T12), where the Name Server has/provides indications of the devices that exist in the Wildcard zone, it is interesting that these queries appear to be optional in state T8 but do not appear to be optional in state T12. This apparent discrepancy is because SCR is also optional and if the target has registered for SCR and is therefore receiving RSCNs, it will likely be querying the Name Server - which is typical/existing behavior. Overall it would appear that these target port queries are purely optional. Number: 7 Author: HP Subject: Sticky Note Date: 9/24/ :33:23 AM HP-010:T::Key Factors in favor of registered vote: 1. No big advantage for the SAN administrator as claimed, except zoning configuration everything else still needs to be done by a SAN trained administrator 2. New requirements (features) on Initiators, Fabric and Targets 3. Targets are more of a concern than the other two, although the max complexity is in the switch 4. Would need to make sure Storage is compliant to this spec extra development work for all our storage arrays a. Need to make sure all the FC registrations performed as defined b. Need to establish Session Begin and Session End protocols c. Strictly follow RSCN rules, etc 5. Likely to lead to two sets of qualification requirements (increased costs), or maybe three, only SCM devices, only non-scm devices or possibly a mix of both, and potentially new interoperability issues With Regard to 256 N_Port restrictions, hp views the restrictions in the document as 'minimum supported/required' values: Min 256 Name Server entries (WKA FFFFFC) Min 256 Unzoned Name Server entries (WKA FFFFFA) Min 256 Zones Min 256 Entries in the Fabric Configuration database Min 256 HBA entries in the HBA Management Server Database HP is not familiar with these values for all hardware manufacturer's, but based on the manufacturers that HP is familiar with, we assume that these values are already present/surpassed in existing hardware. The concern is that these numbers appear to be too high for a simple 'entry level' SAN that this document is assuming. The Zoning requirement is the one that stands out the most, since the implementation proposed in this document is geared to only the single Wildcard Zone. Number: 8 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:04:28 AM brocade-001:e::missing space. Number: 9 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:04:49 AM brocade-002:e::130 Holger Way Number: 10 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:32:12 AM Emulex-003:E::Address, Voice, and Fax for Carlson are inconsistent with the T11 Officers' data base, including he now lists no Fax:Change to 4601 Dean Lakes Blvd. Shakopee, MN Voice: **RESOLUTION: Number: 11 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:05:01 AM brocade-003:e::95134 Number: 12 Author: bnixon Subject: Highlight Date: 9/24/2010 9:32:01 AM Emulex-001:E::Incomplete telephone number for Wilson:Change to **RESOLUTION: Number: 13 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:05:12 AM brocade-004:e:: Number: 14 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:05:22 AM brocade-005:e::delete all Fax numbers. Number: 15 Author: bnixon Subject: Highlight Date: 9/24/2010 9:31:57 AM

5 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Release Notes: Rev v0-25 May a) Initial version of technical report. Rev v1-08 July 2008 a) Modification requested by working group to modify the Scope clause to limit the applicability to only apply to end devices that implement the SCSI-FCP FC-4. b) Changes from June ad hoc meeting - restore document without OLZ Rev v0 12 December 2008 a) Incorporated necessary part of v2 in 4.1 b) Incorporated v5 Rev v1 2 April 2009 a) Updated formatting and variable a) Changes to be consistent with T11 template A) removed byte ordering clause B) updated editorial conventions clause b) Incorporated v3 Rev v2 2 June 2009 a) Changes from Conference call Rev v3 3 August 2009 a) Changes from June Ad Hoc b) Fixed format for transition statements in Initiator state machine Rev v4 5 August 2009 a) Added v5 b) Additional modifications from working group c) Changed all Nx_Ports to N_Ports as this technical report limits use to N_Ports. Rev v5 23 September 2009 a) Added changes from v2 b) Removed 5.4 header as this is covered in 7.3 c) Removed 5.5 header as this is covered in ii

6 This page contains no comments

7 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 d) Made state transition wording format consistent Rev v6 06 October 2009 a) Added changes from v1 Rev v7 08 December 2009 a) Added changes from v2 b) Added changes from v0 c) Removed prohibited, invocable, and allowed Rev v0 04 August 2010 a) Incorporated all comment resolutions from v6 b) Incorporated v3 c) Incorporated v2 iii

8 This page contains no comments

9 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 BSR INCITS xxx-200x American National Standard for Information Technology Fibre Channel Simplified Configuration and Management (FC-SCM) Secretariat Information Technology Industry Council Approved (not yet approved) American National Standards Institute, Inc. Abstract This Technical Report describes a simplified Fibre Channel configuration and management. The Physical Interface 1 requirements are described in Fibre Channel-Physical Interfaces - 2 (FC-PI-2). The Framing and Signaling requirements are described in Fibre Channel-Physical Framing and Signaling - 2 (FC-FS-2). This Technical Report is rec- 3 2 ommended for new implementations, but does not obsolete the existing Fibre Channel standards. iv

10 Page: 4 Number: 1 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:05:53 AM brocade-006:e::fc-pi-2 is a pretty old standard:update to current standard. Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:06:24 AM brocade-008:t::this sentence should be removed as it provides no value. Number: 3 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:06:04 AM brocade-007:e::update to FC-FS-3.

11 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 This technical report is one in a series produced by the American National Standards Committee, INCITS, 1 Information Technology. The secretariat for INCITS is held by the Computer and Business Equipment Manufacturers Association (CBEMA), 1250 Eye Street, NW Suite 200, Washington DC As a by-product of the standards development process and the resources of knowledge devoted to it, INCITS from time to time produces Technical Reports. Such Technical Reports are not standards, nor are they intended to be used as such. INCITS Technical Reports are produced in some cases to disseminate the technical and logical concepts reflected in standards already published or under development. In other cases, they derive from studies in areas where it is found premature to develop a standard due to a still changing technology, or inappropriate to develop a rigorous standard due to the existence of a number of viable options, the choice of which depends on the user's particular requirements. These Technical Reports, thus, provide guidelines, the use of which can result in greater consistency and coherence of information processing systems. When the draft technical report is completed, the Technical Committee approval process is the same as for a draft standard. Processing by INCITS is also similar to that for a draft standard. CAUTION: The developers of this technical report have requested that holder's of patents that may be required for the implementation of this technical report disclose such patents to the publisher. However, neither the developers nor the publisher have undertaken a patent search in order to identify which, if any, patents may apply to this technical report. As of the date of publication of this technical report and following calls for the identification of patents that may be required for the implementation of this technical report, no such claims have been made. No further patent search is conducted by the developer or the publisher in respect to any technical report it processes. No representation is made or implied that licenses are not required to avoid infringement in the use of this technical report. Published by American National Standards Institute 11 West 42nd Street, New York, NY Copyright 200x by American National Standards Institute All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, 2 without prior written permission of ITI, 1250 Eye Street NW, Washington, DC Printed in the United States of America v

12 Page: 5 Number: 1 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:06:58 AM brocade-009:e::update the sentence and change the INCITS secretariat address to 1101 K Street NW Suite 610, Washington, DC globally. Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:07:33 AM brocade-010:e::update address

13 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Foreword (This Foreword is not part of American National Standard INCITS xxx-200x.) The Fibre Channel Simplified Configuration and Management (FC-SCM) technical report describes the Fibre Channel requirements for an easy-to-use limited SAN configuration. This technical report was developed by Task Group T11 of Accredited Standards Committee INCITS during x. The technical report approval process started in 200x. This document includes annexes that are informative and are not considered part of the technical report. Requests for interpretation, suggestions for improvements or addenda, or defect reports are welcome. They should 3 be sent to the INCITS Secretariat, Information Technology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC This technical report was processed and approved for submittal to ANSI by the International Committee for Information Technology Standards (INCITS). Committee approval of the technical report does not necessarily imply that all committee members voted for approval. At the time it approved this technical report, INCITS had the following members: (to be filled in by INCITS) vi

14 Page: 6 Number: 1 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:08:02 AM brocade-012:e:: Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:07:51 AM brocade-011:e:: Number: 3 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:08:16 AM brocade-013:e::update address

15 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Technical Committee T11 on FibreChannelFibre Channel Interfaces, which reviewed this standardtechnical report, had the following members: Steve Wilson, Chair Claudio DeSanti, Vice-Chair Bob Nixon, Secretary (to be filled in prior to submission to INCITS) vii

16 This page contains no comments

17 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Task Group T11.3 on Interconnection Schemes, which developed and reviewed this standardtechnical report, had the following members: Craig W. Carlson, Chair William Martin, Vice-Chair Landon Noll, Secretary (to be filled in prior to submission to INCITS) viii

18 This page contains no comments

19 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Introduction FC-SCM is one of the Fibre Channel family of documents. This family includes FC-FS-3, which specifies the Framing and Signalling Interface and FC-PI-5, which specifies the Physical Interface; i.e., cables, connectors, transceivers. FC-SCM describes a simplified configuration and management for Fibre Channel. The primary upper layer protocol 1 2 (called FC-4) for which provisions are made in this document is FCP-4 (Fibre Channel Protocol for SCSI). Acknowledgements The technical editor would like to thank the following individuals for their special contributions to this standard (alphabetically): tbd ix

20 Page: 9 Number: 1 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:08:48 AM brocade-015:e::(i.e., FC-4) Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:08:32 AM brocade-014:e::(i.e., Fibre Channel Protocol for SCSI)

21 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Contents Page 1 Scope Normative References Normative references Approved references References under development Other references Definitions, symbols, abbreviations, and conventions Definitions Keywords Editorial conventions Feature Set table terms, definitions, and abbreviations Structure and Concepts Management Tool Requirements Overview Generic Services Management Tool Usage Management Tool Requirements on Other Elements HBA Requirements to support the Management tool Requirements for Hosts Overview Generic Services Registration Requirements for initiator FCP_Ports Overview Initiator FCP_Port operation Requirements for Fabrics Overview Generic Service requirements for a Fabric Mandatory Name Server Features Mandatory Fabric Configuration Server attributes and requests Mandatory Unzoned Name Server requests Mandatory Zone Server requests Mandatory HBA Management Server attributes and requests Switch operation Requirements for Storage Overview Generic Services Registration Target FCP_Port state machines overview Initialization state machine PLOGI/PRLI state machine RSCN state machine Target internal change state machine x

22 This page contains no comments

23 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August Requirements for an FCP_Port with initiator and target functions Overview Requirements Annex A (Normative) Retry Rules A.1 Summary A.2 Initiator FCP_Ports or target FCP_Ports A.2.1 LS_RJT or Reject CT_IU A.2.2 Timeout A.2.3 Reject reason code handling A Summary A LS_RJT retryable Reason Codes A Reject CT_IU retryable Reason Codes A Directory Service specific Reject CT_IU retryable Reason Codes xi

24 This page contains no comments

25 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Figure Page 1 Interoperability Architecture Initiator FCP_Port state machine Switch state machine Target FCP_Port state machines xii

26 This page contains no comments

27 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 Table Page Table 1 Numbering Conventions Table 2 Port Name Server attributes provided to Host by HBA Table 3 Fabric Configuration Server attributes provided to Host by HBA Table 4 HBA Management Server Host Bus Adapter attributes provided per port to Host by HBA11 Table 5 HBA Management Server Host Bus Adapter attributes provided to Host by HBA Table 6 Name Server attributes registered by Host Table 7 Fabric Configuration Server attributes registered by Host Table 8 HBA Management Server Host Bus Adapter per-port attributes registered by Host..13 Table 9 HBA Management Server Host Bus Adapter attributes registered by Host Table 10 Name Server requests supported by Switch Table 11 Fabric Configuration Server attributes supported by Switch Table 12 Fabric Configuration Server requests supported by Switch Table 13 Zone Server Attributes supported by Switch Table 14 Zone Server requests supported by Switch Table 15 HBA Management Server Host Bus Adapter attributes supported by Switch Table 16 HBA Management Server requests supported by Switch Table 17 Name Server attributes registered by Storage Device Table 18 Fabric Configuration Server attributes registered by Storage Device Table 19 Retryable LS_RJT Reason Codes/Reason Code Explanations Table 20 Retryable Reject CT_IU Reason Codes/Reason Code Explanations Table 21 Directory Service retryable Reject CT_IU Reason Codes/Reason Code Explanations50 1 xiii

28 Page: 13 Number: 1 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:32:21 AM Emulex-004:E::Ugly format overflow:easiest fix would be to go to the table title and change "Host Bus Adapter attributes" to HBA attributes"**resolution:

29 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August Scope The scope of this technical report includes all of the elements necessary to provide a small, easily manageable 1 SAN environment. It is the intention of this technical report to provide a SAN environment that can be managed by one part-time person who is not skilled in IT management. This technical report is not oriented toward management of a large SAN by an IT department with SAN management experts. This technical report requires some features that are in the referenced ANSI/INCITS standards. 2 This technical report identifies the mechanisms necessary for a management tool to promote successful management of a SAN by those not skilled in the management of a SAN. An additional objective of this technical report is to simplify implementations and their associated documentation, testing, and support requirements. This technical report is applicable only to end devices that implement the SCSI-FCP FC-4. Implementations of other FC-4 protocols are not included in the scope of this technical report. Internal characteristics of conformant implementations are not defined by this technical report. This technical report incorporates features from the standards and technical reports described in clause 2. 1

30 Page: 14 Number: 1 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:09:37 AM brocade-016:t::remove this sentence as it does not reflect the content of this technical report. Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:09:25 AM brocade-017:t::i do not believe this technical report can be successfully managed by anyone not skilled in SAN management.

31 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August Normative References 2.1 Normative references The following standards contain provisions that, by reference in the text, constitute provisions of this technical report. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this technical report are encouraged to investigate the possibility of applying the most recent editions of the standards listed below. Copies of the following documents may be obtained from ANSI: approved ANSI standards, approved and draft international and regional standards (ISO, IEC, CEN/CENELEC, ITUT), and approved and draft foreign standards (including BSI, JIS, and DIN). For further information, contact ANSI Customer Service Department at (phone), (fax) or via the World Wide Web at Additional availability contact information is provided below as needed. 2.2 Approved references ASCII: ISO/IEC 646:1991, Information technology - ISO 7-bit coded character set for information interchange (third edition) FC-AL-2: ISO/IEC :2005, Fibre Channel-Arbitrated Loop 2 (FC-AL-2) [ANSI INCITS (R2004)] FC-AL-2 AM1:ANSI INCITS /AM1-2003, Fibre Channel-Arbitrated Loop 2 (FC-AL-2) Amendment 1 5 FC-FS-2: 67 FC-GS-5: 89 FC-HBA: 10 FC-LS: 11 FCP-2: 12 FCP-3: 13 FC-SP: FC-SW-4: SM-HBA: ANSI INCITS , Fibre Channel Framing and Signalling, second generation (FC-FS-2) ANSI INCITS , Fibre Channel Generic Services, fifth generation (FC-GS-5) ANSI INCITS , Host Bus Adapter Tool Programming Interface (FC-HBA) ANSI INCITS , Fibre Channel Link Services (FC-LS) ANSI INCITS , SCSI Fibre Channel Protocol - 2 (FCP-2) ANSI INCITS , SCSI Fibre Channel Protocol - 3 (FCP-3) ANSI INCITS , Fibre Channel - Security Protocol (FC-SP) ANSI INCITS , Fibre Channel Switch Fabric - 4 (FC-SW-4) ANSI INCITS , Host Bus Adapter Application Programming Interface (SM_HBA) References under development At the time of publication, the following referenced standards were still under development. For information on the current status of the document, or regarding availability, contact the relevant standards body or other organization as indicated. FC-FS-3: ANSI INCITS xxx-200x, Fibre Channel Framing and Signalling, third generation (FC-FS-3) 2

32 Page: 15 Number: 1 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:32:50 AM Emulex-007:E::According to a notification from Harvey Rosenfeld in October 200, draft foreign standards and BSI standards are no longer available from ANSI:Change to "approved foreign standards (including JIS and DIN)""**RESOLUTION: Number: 2 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:32:43 AM Emulex-005:E::According to a notification from Harvey Rosenfeld in May 2007, regional standards are no longer available from ANSI:Remove "and regional"**resolution: Number: 3 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:32:32 AM Emulex-006:E::According to a notification from Harvey Rosenfeld in May 2007, CEN/CENELEC and ITUT standards are no longer available from ANSI:Change to "ISO and IEC"**RESOLUTION: Number: 4 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:33:02 AM Emulex-008:E::According to a notification from Harvey Rosenfeld in May 2007, the ANSI customer service phone number has changed its suffix:change to " "**RESOLUTION: Number: 5 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:10:17 AM brocade-018:e::fc-fs-2: ANSI INCITS , Fibre Channel Framing and Signalling, second generation (FC-FS-2) Number: 6 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:10:29 AM brocade-019:e::fc-gs-5: ANSI INCITS , Fibre Channel Generic Services, fifth generation (FC-GS-5) Number: 7 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:33:07 AM Emulex-009:E::GS-6 has been published as ANSI INCITS :Update this reference to FC-GS-6**RESOLUTION: Number: 8 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:10:48 AM brocade-020:e::fc-hba: ANSI INCITS , Host Bus Adapter Tool Programming Interface (FC-HBA) Number: 9 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:33:15 AM Emulex-010:E::FC-HBA is no longer cited in this technical report:remove this reference to FC-HBA**RESOLUTION: Number: 10 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:11:08 AM brocade-021:e::fc-ls: ANSI INCITS , Fibre Channel Link Services (FC-LS) Number: 11 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:12:06 AM brocade-022:e::fcp-2: ANSI INCITS , SCSI Fibre Channel Protocol - 2 (FCP-2) Number: 12 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:12:23 AM brocade-023:e::fcp-3: ANSI INCITS , SCSI Fibre Channel Protocol - 3 (FCP-3) Number: 13 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:12:38 AM brocade-024:e::fc-sp: ANSI INCITS , Fibre Channel - Security Protocol (FC-SP) Number: 14 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:12:55 AM brocade-025:e::fc-sw-4: ANSI INCITS , Fibre Channel Switch Fabric - 4 (FC-SW-4) Number: 15 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:41:38 AM Emulex-011:E::SW-5 has been published as ANSI INCITS :Update this reference to FC-SW-5**RESOLUTION: Number: 16 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:13:13 AM brocade-026:e::sm-hba Number: 17 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:41:55 AM Emulex-012:E::There are differing approaches for listing references in development. I prefer the one that identifies the INCITS project number (which leads to a specific work in progress) rather than a speculative publication (which doesn't locate anything):editor's choice**resolution: Number: 18 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:13:29 AM brocade-027:e::framing and Signalling - 3

33 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August FC-GS-6: ANSI INCITS xxx-200x, Fibre Channel Generic Services, sixth generation (FC-GS-6) FC-LS-2: FCP-4: 5 FC-SW-5: FC-SP-2: ANSI INCITS xxx-200x, Fibre Channel Link Services, second generation (FC-LS-2) ANSI INCITS xxx-200x, SCSI Fibre Channel Protocol - 4(FCP-4) 3 ANSI INCITS xxx-200x, Fibre Channel Switch Fabric - 5 (FC-SW-5) ANSI INCITS xxx-200x, Fibre Channel - Security Protocol, second generation (FC-SP-2) 4 6 SM-HBA-2: ANSI INCITS xxx-200x, Storage Management Host Bus Adapter Application Programming Interface 2nd Generation (SM-HBA-2) SPC-4: ANSI INCITS xxx-200x, SCSI Primary Commands - 4 (SPC-4) Other references For information on the current status of the listed document(s), or regarding availability, contact the indicated organization. 3

34 Page: 16 Number: 1 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:42:08 AM Emulex-013:E::GS-6 has been published and GS-7 is now the latest work in progress:update this reference to FC-GS-7**RESOLUTION: Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:13:45 AM brocade-028:e::generic Services - 6 Number: 3 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:13:55 AM brocade-029:e::link Services - 3 Number: 4 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:14:42 AM brocade-030:e::4(fcp-4):add space Number: 5 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:42:22 AM Emulex-014:E::SW-5 has been published and SW-6 is now the latest work in progress:update this reference to FC-SW-6**RESOLUTION: Number: 6 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:15:03 AM brocade-031:e::i don't see any reference to SM-HBA-2 in the document. Number: 7 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:15:29 AM brocade-032:e::2.4 Other references For information on the current status of the listed document(s), or regarding availability, contact the indicated organization.

35 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August Definitions, symbols, abbreviations, and conventions 3.1 Definitions Default Zone: As defined in FC-GS HBA: a combination of hardware, hardware-resident firmware, and Host-resident software that provides to a 4 Host:. a) at least one PN_Port; b) at least one VN_Port; c) the functions of FC-0, FC-1, FC-2, and FC-3 for the VN_Ports it provides; and d) the functions of at least one FC-4 for the VN_Ports it provides Host: a computing system that contains an FCP initiator, provides end user services (e.g., access) and that connects to a SAN Initial FC discovery: The process used by an N_Port compliant with this technical report to determine the 24 bit addresses and World Wide Port Names of FCP_Ports that are also compliant with this technical report Name Server Session Begin bit: As defined in FC-LS RSCN FC discovery: The process used by an N_Port compliant with this technical report to determine the bit addresses and World Wide Port Names of FCP_Ports that are compliant with this technical report after an RSCN is received SCM environment: a SAN that is composed of devices that are compliant with this technical report SCM FC Switch: A Fibre Channel switch that is compliant with clause Wildcard Zone: A zone that provides any to any connectivity between FC-SCM compliant devices. 3.2 Keywords invalid: A keyword used to describe an illegal or unsupported bit, byte, word, field or code value. Receipt by a device server of an invalid bit, byte, word, field or code value shall be reported as error mandatory: A keyword indicating an item that is required to be implemented as defined in this technical report may: A keyword that indicates flexibility of choice with no implied preference may not: A keyword that indicates flexibility of choice with no implied preference option, optional: Keywords that describe features that are not required to be implemented by this technical report. However, if any optional feature defined by this technical report is implemented, then it shall be implemented as defined in this technical report reserved: A keyword referring to bits, bytes, words, fields, and code values that are set aside for future standardization. A reserved bit, byte, word, or field shall be set to zero, or in accordance with a future extension to 4

36 Page: 17 Number: 1 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:16:08 AM brocade-033:e::3.1.2hba:add space Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:16:40 AM brocade-035:e::a Number: 3 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:16:26 AM brocade-034:e::host Number: 4 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:17:14 AM brocade-036:e::host:global change Number: 5 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:17:29 AM brocade-037:e::a Number: 6 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:18:14 AM brocade-039:e::address identifiers or N_Port_IDs Number: 7 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:17:48 AM brocade-038:e::n_port_names Number: 8 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:18:29 AM brocade-040:e::a Number: 9 Author: dpeterso Subject: Cross-Out Date: 9/24/2010 9:18:50 AM brocade-041:e::option, Number: 10 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:19:02 AM brocade-042:e::a keyword

37 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 this technical report. Recipients are not required to check reserved bits, bytes, words, or fields for zero values. Receipt of reserved code values in defined fields shall be reported as error shall: A keyword indicating a mandatory requirement. Designers are required to implement all such mandatory requirements to ensure interoperability with other products that conform to this technical report should: A keyword indicating flexibility of choice with a strongly preferred alternative vendor specific: Something (e.g., a bit, field, code value) that is not defined by this technical report. Specification of the referenced item is determined by the device vendor and may be used differently in various implementations. 3.3 Editorial conventions Certain words and terms used in this technical report have a specific meaning beyond the normal English meaning. These words and terms are defined either in the glossary or in the text where they first appear. Upper case is used when referring to the name of a numeric value defined in this specification or a formal attribute possessed by an entity. When necessary for clarity, names of objects, procedure calls, arguments or discrete states are capitalized or set in bold type. In this technical report, a number of conditions, mechanisms, sequences, parameters, events, states, or similar terms are printed with the first letter of each word in upper-case and the rest lower-case (e.g., Exchange, Sequence). Any lower case uses of these words have the normal technical English meanings An alphanumeric list (e.g., a, b, c) of items indicate the items in the list are unordered. A numeric list (e.g., 1, 2, 3) of items indicate the items in the list are ordered (i.e., item 1 shall occur or complete before item 2). In case of any conflict between figures, tables, and text, the text takes precedence. Exceptions to this convention are indicated in the appropriate sections. In all of the figures, tables, and text of this document, the most significant bit of a binary quantity is shown on the left side. Exceptions to this convention are indicated in the appropriate sections. In the various ladder diagrams that show a sequence of events, the vertical axis (i.e., up and down the page) shows time from top to bottom. Notes and examples do not constitute any requirements for implementors. A binary number is represented in this technical report by any sequence of digits comprised of only the Arabic numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Underscores or spaces may be included in binary number representations to increase readability or delineate field boundaries (e.g., b or 0_0101_1010b). A hexadecimal number is represented in this technical report by any sequence of digits comprised of only the Arabic numerals 0 through 9 and/or the upper-case English letters A through F immediately followed by a lower-case h (e.g., FA23h). Underscores or spaces may be included in hexadecimal number representations to increase readability or delineate field boundaries (e.g., B FD8C FA23h or B_FD8C_FA23h). A decimal number is represented in this technical report by any sequence of digits comprised of only the Arabic numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g., 25). 5

38 Page: 18 Number: 1 Author: rhathorn Subject: Highlight Date: 9/24/2010 9:26:41 AM IBM-001:T::should not check Number: 2 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:42:38 AM Emulex-015:E::State Diagram conventions are not described:steal FC-SW-5 subclause 3.3**RESOLUTION: Number: 3 Author: bnixon Subject: Comment on Text Date: 9/24/2010 9:42:52 AM Emulex-016:T::alphanumeric could include a mix of numbered and lettered list items, which is NOT what we mean:change "alphanumeric" to "alphabetic"**resolution:

39 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August 2010 This technical report uses the following convention for representing decimal numbers: a) the decimal separator (i.e., separating the integer and fractional portions of the number) is a period; b) the thousands separator (i.e., separating groups of three digits in the portion of a number) is a space; and c) the thousands separator is used in both the integer and fractional portion of a number. Table 1 shows some examples of decimal numbers using various conventions. Table 1 Numbering Conventions French English This technical report 0, , , ,95 1,323, When the value of the bit or field is not relevant, x or xx appears in place of a specific value. 3.4 Feature Set table terms, definitions, and abbreviations Features that some but not all of the referenced ANSI/INCITS standards require for compliance may not be referenced in this technical report and if those features are implemented they shall not be required for compliant devices to interoperate as defined in this technical report. There may be some optional features of the referenced ANSI/INCITS standards that are not mutually exclusive, but are required for the purpose of this technical report. Each specification of such a required feature in this technical report identifies the referenced ANSI/INCITS standards in which the feature is defined. Features in this technical report are summarized in the form of Feature Set tables. In several tables within this technical report, there are references to notes associated with the table. These notes are normative and are mandatory requirements of this technical report. 6

40 This page contains no comments

41 T11.3 T11/1824-DT Working Draft T11/Revision 1.1 Simplified Configuration and Management Prepared 04 August Structure and Concepts This technical report defines an environment in which a compliant device adheres to a set of behaviors that allow a management tool to simply manage the SAN of which this device is a component, as shown in figure 1. The SAN consists of one or more hosts (e.g., servers), one or more switches, and one or more storage devices. The management tool may reside on one of the hosts, in one of the switches, or in one of the storage devices. This technical report presumes that changes in the SAN configuration are performed by a single management tool. If multiple management tools are operating concurrently in a single SAN, then coordination of their activities is outside the scope of this technical report. Management Tool Host(s) (e.g., Server) Switch(s) Storage Device(s) Figure 1 Interoperability Architecture This environment encompasses the following areas: a) Management Tool Behavior: The set of behaviors provided by a host, switch, or storage device that a 1 management tool running locally in that host, switch, or storage device may use to manage a SCM environment; b) Host Behavior: The set of behaviors required to allow a Host, including a Host Bus Adapter, to be used to 2 3 manage a SCM environment and be managed in a SCM environment; c) Fabric Behavior: The set of behaviors required to allow a Fabric to be used to manage an SCM 4 environment and be managed in a SCM environment; and d) Storage Behavior: The set of behaviors required to allow a Storage device to be used to manage an SCM 5 environment and be managed in a SCM environment. 7

42 Page: 20 Number: 1 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:19:16 AM brocade-043:e::an Number: 2 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:19:36 AM brocade-045:e::an Number: 3 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:19:24 AM brocade-044:e::an Number: 4 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:19:42 AM brocade-046:e::an Number: 5 Author: dpeterso Subject: Highlight Date: 9/24/2010 9:19:57 AM brocade-047:e::an