ANSI INCITS 443-2008 Fibre Channel C Storage Network Ping (SNPing).pdf

《ANSI INCITS 443-2008 Fibre Channel C Storage Network Ping (SNPing).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 443-2008 Fibre Channel C Storage Network Ping (SNPing).pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Fibre Channel Storage Network Ping (SNPing)ANSI INCITS 443-2008ANSIINCITS443-2008ANSIINCITS 443-2008American National Standardfor Information Technology Fibre Channel Storage Network Ping (SNPing)SecretariatInformation Technology Indus

2、try CouncilApproved May 21, 2008American National Standards Institute, Inc.AbstractThis standard defines a Command Line Interface (CLI) for a storage networking management utility pro-gram that is equivalent to the IP Networking Ping function. The CLI may be directly useful to storagemanagement pers

3、onnel or it may be accessed via other applications (e.g., an SMI-S Client).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

4、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 that a c

5、oncerted 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 procedures n

6、ot 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 Standard in

7、 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 the Amer

8、ican 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 Standar

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

10、tten 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 berequired for the implementation of the standard disclose such patents to the publisher. However,neither

11、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 following calls for the identification of patents that may be required for the implementation ofthe standard, no s

12、uch 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 are not required to avoid infringement in the use of this standard.iContentsPageForeword . iiiIntroduction .vi1 S

13、cope. 12 Normative References . 22.1 Overview 22.2 Approved references 22.3 References under development. 32.4 IETF References 33 Definitions and conventions. 33.1 Overview 33.2 Definitions 33.3 Editorial Conventions. 43.4 Abbreviations, acronyms and symbols 53.5 Keywords . 63.6 Output Format Descri

14、ption Conventions 74 SNPing Command Line Interface 84.1 Overview 84.2 Initialization 104.3 Locate Devices 104.3.1 Overview 104.3.2 Locating the local HBA. 114.3.3 Locating the remote device 114.3.3.1 Overview 114.3.3.2 PingWhat default format 134.3.3.3 PingWhat worldwide name format . 134.3.3.4 Ping

15、What Fibre Channel address identifier format 134.3.3.5 PingWhat IP address format 134.3.4 Returning information about the located local HBA and remote device . 144.4 Response Test. 154.4.1 Overview 154.4.2 Command line logical unit number format . 174.5 Closing Output . 18AnnexesA SNPing Augmented B

16、ackus-Naur Form Definition 19A.1 SNPing command line ABNF. 19A.2 SNPing output ABNF . 20A.2.1 Overview 20iiPageA.2.2 Output from -version option ABNF. 20A.2.3 Output from -D option ABNF 20A.2.4 Output from -d option ABNF 20A.2.5 Output from -a option ABNF 20A.2.6 Output from Ping Step . 20A.2.7 Outp

17、ut from -z 21A.2.8 References 21A.2.9 Rules copied from RFCs 3986. 21B Example SNPing man page. 22Tables1 ISO and American conventions . 52 SNPing application steps. 83 Options processed during SNPing initialization . 104 Options that select how the local HBA is chosen 115 Options that specify how t

18、o locate the remote device . 116 Options for returning information about the located devices . 147 Options that select how the SNPing is performed . 158 Options that select the SNPing transaction for fibre channel remote devices. 169 Options that select the SNPing transaction for SAS remote devices

19、1610 Options that select the SNPing transaction for iSCSI remote devices 1711 Options processed while closing SNPing 18Figure1 SNPing interface layering 1iiiForeword (This foreword is not part of American National Standard ANSI INCITS 443-2008.)This standard defines a Command Line Interface (CLI) fo

20、r a storage networking man-agement utility program that is equivalent to the IP Networking Ping function. The CLImay be directly useful to storage management personnel or it may be accessed viaother applications (e.g., an SMI-S Client).This standard was developed by Task Group T11 of Accredited Stan

21、dards Commit-tee INCITS during 2006-2008. The approval process started in 2005.This standard contains two annexes. Annex A is normative and is considered part ofthis standard. Annex B is informative and is not considered part of this standard.Users of this standard are encouraged to determine if the

22、re are standards in develop-ment or new versions of this standard that may extend or clarify technical informationcontained in this standard.Requests for interpretation, suggestions for improvements or addenda, or defect re-ports are welcome. They should be sent to the INCITS Secretariat, Informatio

23、n Tech-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 InterNation-al Committee for Information Technology Standards (INCITS). Committee approvalof the standard does not necessarily imply that al

24、l committee members voted for itsapproval. At the time it approved this standard, INCITS had the following members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc Steve ZillesScott Foshee (Alt.)AIM Global Dan MullenCharles Biss (Al

25、t.)Apple Computer, Inc. David MichaelDistributed Managment Task Force . Tony DiCenzoElectronic Industries Alliance Edward Mikoski, Jr.EMC Corporation Gary RobinsonFarance, Inc Frank FaranceTimothy Schoechle (Alt.)Google Zaheda BhoratGS1 US Ray DelnickiFrank Sharkey (Alt.)James Chronowski (Alt.)Mary

26、Wilson (Alt.)Hewlett-Packard Company. Karen HigginbottomSteve Mills (Alt.)Scott Jameson (Alt.)IBM Corporation . Ronald F. SillettiRobert Weir (Alt.)Sandy Block (Alt.)Richard Schwerdtfeger (Alt.)IEEE . Judith GormanTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodi Haasz (Alt.)Bob Labelle (Alt.)Susan Tatine

27、r (Alt.)ivOrganization Represented Name of RepresentativeIntel. Philip WennblomDave Thewlis (Alt.)Grace Wei (Alt.)Lexmark International. Don WrightDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft Corporation . Jim HughesDave Welsh (Alt.)Isabelle Valet-Harper (Alt.)National Institute of Standards b) ap

28、proved international standards (ISO and IEC); andc) approved foreign standards (including JIS and DIN).For further information, contact the ANSI Customer Service Department:Phone +1 212-642-4980Web: http:/www.ansi.orgFor printed versions of ANSI standards listed here, contact:Global Engineering Docu

29、mentsWeb: http:/Phone: +1 800-854-7179Post: 15 Inverness Way East, Englewood, CO 80112-5704For further information regarding ISO standards, contact the ISO Customer Service Department:Phone +41 22 749 01 11Fax: +42 22 733 34 30E-mail: salesiso.orgPost: ISO, 1, ch. de la Voie-Creuse, Case postale 56,

30、 CH-1211, Geneva 20 SwitzerlandAdditional availability contact information is provided below as needed.2.2 Approved referencesANSI INCITS 424-2007, Fibre Channel - Framing and Signaling-2 (FC-FS-2).ANSI INCITS 428-2006, Storage Management Host Bus Adapter Application Programming In-terface (SM-HBA).

31、ANSI INCITS 427-2006, Fibre Channel - Generic Services-5 (FC-GS-5).ANSI INCITS 402-2005, SCSI Architecture Model - 3 (SAM-3).ANSI INCITS 417-2006, Serial Attached SCSI - 1.1 (SAS-1.1).ANSI INCITS 411-2007, iSCSI Management API (IMA).ANSI INCITS 443-200832.3 References under developmentAt the time of

32、 publication, the following referenced standards and technical reports were still underdevelopment. For information on the current status of the documents, or regarding availability, con-tact the relevant standards body or other organization as indicated.INCITS Project: 1841-D, Storage Management Ho

33、st Bus Adapter Application Programming In-terface 2nd Generation (SM-HBA-2).2.4 IETF ReferencesCopies of the following approved IETF standards may be obtained through the Internet EngineeringTask Force (IETF) at www.ietf.org.RFC 791, Internet Protocol.RFC 1035, Domain names - implementation and spec

34、ification.RFC 3720, Internet Small Computer Systems Interface (iSCSI).RFC 3721, Internet Small Computer Systems Interface (iSCSI) Naming and Discovery.RFC 3986, Uniform Resource Identifier (URI): Generic Syntax.RFC 4234, Augmented BNF for Syntax Specifications.RFC 4291, IP Version 6 Addressing Archi

35、tecture.RFC 4501, Domain Name System Uniform Resource Identifiers.3 Definitions and conventions3.1 OverviewFor SNPing, the following definitions, conventions, abbreviations, acronyms, and symbols apply.3.2 Definitions3.2.1 address identifier: A Fibre Channel address value used to identify source or

36、destination of aframe (see FC-FS-2).3.2.2 application: The program that processes the CLI defined in this standard and produces theoutputs defined in this standard.3.2.3 command line interface (CLI): The command-line inputs to an application (see 3.2.2).3.2.4 decimal digit: One of the following char

37、acters 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9 thatrepresents one digit in a decimal number.3.2.5 DNS host name: The host name returned by an Internet Domain Name Server (see RFC1035).3.2.6 FC-GS-5 host name: The host name associated with a Fibre Channel port (see FC-GS-5).ANSI INCITS 443-200843.2.7 HBA ide

38、ntifier: An address identifier (see 3.2.1) used by an HBA (see 3.2.9).3.2.8 hexadecimal digit: One of the following characters 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A,B, C, D, E, F, a, b, c, d, e, or f that represents one digit in a hexadecimal number.3.2.9 Host Bus Adapter (HBA): A hardware component toget

39、her with its supporting software thatprovides an interface from an operating system to one or more links (see SM-HBA).3.2.10 IP address: An IPv4 address (see 3.2.11) or an IPv6 address (see 3.2.12).3.2.11 IPv4 address: An Internet Protocol version 4 address (see RFC 791).3.2.12 IPv6 address: An Inte

40、rnet Protocol version 6 address (see RFC 4291).3.2.13 iSCSI alias: An alias string can also be associated with an iSCSI Node (see RFC 3720).3.2.14 iSCSI name: The worldwide unique name of an iSCSI initiator or iSCSI target (see RFC3720).3.2.15 iSCSI target name: The worldwide unique name of an iSCSI

41、 target (see RFC 3720).3.2.16 Name Server: A Server that allows registration and reporting of various objects. See FC-GS-5.3.2.17 node name: An identifier associated with a node (see FC-FS-2).3.2.18 port name: An N_Port_Name (see FC-FS-2).3.2.19 Server: An entity that accepts CT requests and provide

42、s CT responses. A Server is access-ed via a Service (e.g., the Name Server is accessed using the Directory Service). See FC-GS-5.3.2.20 Service: A service provided by a node, accessible via an N_Port that is addressed by aWell-Known Address (e.g., the Directory Service and the Alias Service). A Serv

43、ice provides access toone or more Servers. See FC-GS-5.3.2.21 stdout: The data stream where a program writes its output data.3.2.22 worldwide name: An identifier that is worldwide unique (see FC-FS-2).3.3 Editorial ConventionsIn this standard, a number of conditions, mechanisms, sequences, parameter

44、s, events, states, orsimilar terms are printed with the first letter of each word in uppercase and the rest lowercase (e.g.,Exchange, Class). Any lowercase uses of these words have the normal technical English meanings.Lists sequenced by letters (e.g., a-red, b-blue, c-green) show no ordering relati

45、onship between thelisted items. Numbered lists (e.g., 1-red, 2-blue, 3-green) show an ordering between the listed items.ANSI INCITS 443-20085The ISO convention of numbering is used (i.e., the thousands and higher multiples are separated bya space and a comma is used as the decimal point.) A comparis

46、on of the American and ISO con-ventions are shown in table 1.In case of any conflict between figure, table, and text, the text, then tables, and finally figures takeprecedence. Exceptions to this convention are indicated in the appropriate sections.In all of the figures, tables, and text of this doc

47、ument, the most significant bit of a binary quantity isshown on the left side. Exceptions to this convention are indicated in the appropriate sections.When the value of the bit or field is not relevant, x or xx appears in place of a specific value.Numbers that are not immediately followed by lower-c

48、ase b or h are decimal values.Numbers immediately followed by lower-case b (xxb) are binary values.Numbers or upper case letters immediately followed by lower-case h (xxh) are hexadecimal values.3.4 Abbreviations, acronyms and symbolsAbbreviations and acronyms applicable to this standard are listed.

49、 Definitions of several of theseitems are included in 3.2.ABNF Augmented Backus-Naur Form (see RFC 4234)CLI Command Line Interface (see 3.2.3)CT Common Transport, see FC-GS-5CT_IU Common Transport Information Unit, see FC-GS-5DNS Domain Name System (see RFC 1035)FC Fibre ChannelHBA Host Bus AdapterIMA iSCSI Management API (see 2.2)IP Internet ProtocolIPv4 Internet Protocol version 4 (see RFC 791)IPv6 Internet Protocol version 6 (see RFC 4291)iSCSI internet SCSI (see