1、American National StandardDeveloped byfor Information Technology Storage Management Part 1: Common ArchitectureINCITS 388.1-2011INCITS 388.1-2011INCITS 388.1-2011Revision and Partition ofINCITS 388-2008American National Standardfor Information Technology Storage Management Part 1: Common Architectur
2、eSecretariatInformation Technology Industry CouncilApproved February 11, 2011 American National Standards Institute, Inc.AbstractThis specification defines an interface between WBEM-capable clients and servers for the secure, exten-sible, and interoperable management of networked storage.Approval of
3、 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 ofStandards Review, substantial agreement has been reached
4、 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 their resolution.The use of American National Standards
5、 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 American National Standards Institute does not deve
6、lop 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 Standards Institute. Requests for interpretations sh
7、ould 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 require that action be taken periodically to reaffirm
8、, 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 Standards Institute, Inc.25 West 43rd Street, New York,
9、 NY 10036Copyright 2011 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, 1101 K Street NW, Suite 610 Washington, DC 20005. Printed in t
10、he United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may be re-quired for the implementation of the standard disclose such patents to the publisher. However, nei-ther the developers nor the publisher have undertaken a patent search in order
11、to identify which, ifany, patents may apply to this standard. As of the date of publication of this standard, followingcalls for the identification of patents that may be required for the implementation of the standard,notice of one or more such claims has been received. By publication of this stand
12、ard, no positionis taken with respect to the validity of this claim or of any rights in connection therewith. The knownpatent holder(s) has (have), however, filed a statement of willingness to grant a license underthese rights on reasonable and nondiscriminatory terms and conditions to applicants de
13、siring to ob-tain such a license. Details may be obtained from the publisher. No further patent search is con-ducted by the developer or publisher in respect to any standard it processes. No representation ismade or implied that this is the only license that may be required to avoid infringement in
14、the use ofthis standard.iContentsForeword viiIntroduction ix1. Scope .12. Normative references .32.1 General 32.2 Approved references 32.3 DMTF references (Final) 32.4 IETF references (standards or draft standards). 32.5 References under development. 42.6 Other references 43. Definitions, symbols, a
15、bbreviations, and conventions.73.1 Definitions 73.2 Acronyms and abbreviations 113.3 Keywords . 113.4 Conventions . 124. Typographical Conventions 134.1 Experimental Maturity Level. 134.2 Implemented Maturity Level. 134.3 Stable Maturity Level 144.4 Finalized Maturity Level . 144.5 Deprecated Materi
16、al. 145. Transport and Reference Model175.1 Introduction 175.2 Transport Stack 185.3 Reference Model 196. Health and Fault Management.216.1 Objectives 216.2 Overview 216.3 Terms. 216.4 Description of Health and Fault Management 227. Object Model General Information 337.1 Model Overview (Key Resource
17、s) 337.2 Techniques. 348. Correlatable and Durable Names 378.1 Overview 378.2 Guidelines for SCSI Logical Unit Names . 388.3 Guidelines for FC-SB-2 Device Names 388.4 Guidelines for Port Names. 398.5 Guidelines for Storage System Names 398.6 Standard Formats for Correlatable Names 408.7 Testing Equa
18、lity of correlatable Names . 478.8 iSCSI Names 489. Policy .519.1 Objectives 519.2 Overview 519.3 Policy Terms 519.4 Policy Definition 529.5 Policy Recipes 53ii10. Standard Messages 5510.1 Overview 5510.2 Required Characteristics of Standard Messages. 5510.3 Message Registry 5711. Service Discovery.
19、10111.1 Objectives 10111.2 Overview 10111.3 SLP Messages. 10311.4 Scopes . 10411.5 Services Definition . 10511.6 User Agents (UA). 10611.7 Service Agents (SAs). 10711.8 Directory Agents (DAs) 10811.9 Service Agent Server (SA Server) . 10811.10 Configurations 11111.11 Standard WBEM Service Type Templ
20、ates. 11412. SMI-S Roles .11912.1 Introduction 11912.2 SMI-S Client. 12012.3 Dedicated SMI-S Server 12012.4 General Purpose SMI-S Server . 12212.5 Directory Server . 12312.6 Combined Roles on a Single System. 12413. Installation and Upgrade12513.1 Introduction 12513.2 Role of the Administrator 12513
21、.3 Goals 12513.4 Device Support. 12613.5 WBEM Service Support the model isdefined in the other specification parts.Parts of this StandardThis standard is subdivided into the following parts: INCITS 388.0, Information Technology Storage Management Technical Specification Overview INCITS 388.1, Inform
22、ation Technology Storage Management Technical Specification Part 1: CommonArchitecture INCITS 388.2, Information Technology Storage Management Technical Specification Part 2: CommonProfiles INCITS 388.3, Information Technology Storage Management Technical Specification Part 3: Block Devices INCITS 3
23、88.4, Information Technology Storage Management Technical Specification Part 4: File Systems INCITS 388.5, Information Technology Storage Management Technical Specification Part 5: Fabric INCITS 388.6, Information Technology Storage Management Technical Specification Part 6: Host Elements INCITS 388
24、.7, Information Technology Storage Management Technical Specification Part 7: MediaLibrariesINCITS 388.1-2011xAMERICAN NATIONAL STANDARD INCITS 388.1-2011American National Standardfor Information Technology Storage Management Part 1: Common Architecture1Clause 1: ScopeINCITS 388.1, Information Techn
25、ology Storage Management Technical Specification Part 1: CommonArchitecture defines the core architecture and protocols in SMI-S. The components of SMI-S architecture include: Transport - communicating management information between constituents of the management system Health and fault management -
26、 detecting failures through monitoring the state of storage components General information about the object model Names - how SMI-S uses names to allow applications to correlate across SMI-S and to other standards Policy - the expression of management behavior such that administrators and other mana
27、gement software cancontrol that behavior, tailoring it to accomplish specific goals. Standard messages - how exceptions are presented to client applications Service discovery - techniques clients use to discover SMI-S services Installation and upgrade - recommendations for implementations Compliance
28、 - requirement for compliance to the standardINCITS 388.1-2011 Scope2Normative references INCITS 388.1-20113Clause 2: Normative references2.1 GeneralThe following standards contain provisions which, through reference in this text, constitute provisions of thisAmerican National Standard. All standard
29、s are subject to revision, and parties to agreements based on thisAmerican National Standard are encouraged to investigate the possibility of applying the most recent editions ofthe standards indicated below.The following referenced documents are indispensable for the application of this document. F
30、or dated references,only the edition cited applies. For undated references, the latest edition of the referenced document (including anyamendments) applies.2.2 Approved referencesISO/IEC 14776-413, SCSI Architecture Model - 3 (SAM-3) ANSI INCITS 402-200xISO/IEC 14776-452, SCSI Primary Commands - 3 (
31、SPC-3) ANSI INCITS.351-2005ANSI/INCITS 374:2003, Information technology - Fibre Channel Single - Byte Command Set-3 (FC-SB-3)2.3 DMTF references (Final)DMTF Final documents are accepted as standards. For DMTF Draft or Preliminary documents, see 2.5.DMTF DSP0004 CIM Infrastructure Specification 2.3.0
32、http:/www.dmtf.org/standards/published_documents/DSP0004V2.3_final.pdfDMTF DSP0200 CIM Operations over HTTP 1.1.0http:/www.dmtf.org/standards/documents/WBEM/DSP200.htmlDMTF DSP0201 Representation of CIM in XML 2.2.0http:/www.dmtf.org/standards/published_documents/DSP201.htmlDMTF DSP0202 CIM Query La
33、nguage Specification 1.0.0http:/www.dmtf.org/standards/published_documents/DSP0202_1.0.0.pdfDMTF CIM Schema 2.15.0http:/www.dmtf.org/standards/cim/cim_schema_v2152.4 IETF references (standards or draft standards)For IETF Informational documents and proposed standards, see 2.5.IETF RFC 2045, Multipur
34、pose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodieshttp:/www.ietf.org/rfc/rfc2045.txtIETF RFC 2246, The TLS Protocol Version 1.0http:/www.ietf.org/rfc/rfc2246.txtIETF RFC 4291, IP Version 6 Addressing ArchitectureIETF RFC 2396, Uniform Resource Identifiers (URI)http:/www
35、.ietf.org/rfc/rfc2396.txtIETF RFC 2608, Service Location Protocol, Version 2http:/www.ietf.org/rfc/rfc2608.txtINCITS 388.1-2011 Normative references4IETF RFC 2609, Service Templates and Service: Schemeshttp:/www.ietf.org/rfc/rfc2609.txtIETF RFC 2610, DHCP Options for Service Location Protocolhttp:/w
36、ww.ietf.org/rfc/rfc2610.txtIETF RFC 2616, Hypertext Transfer Protocol - HTTP/1.1 http:/www.ietf.org/rfc/rfc2616.txtIETF RFC 2617, HTTP Authentication: Basic ad Digest Access Authenticationhttp:/www.ietf.org/rfc/rfc2617.txtIETF RFC 2445, Internet Calendaring and Scheduling Core Object Specification (
37、iCalendar)http:/www.ietf.org/rfc/rfc2445.txtIETF RFC 3280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profilehttp:/www.ietf.org/rfc/rfc3280.txtIETF RFC 3723, Securing Block Storage Protocols over IPhttp:/www.ietf.org/rfc/rfc3723.txtIETF RFC 3986, Defin
38、itions of Managed Objects for the DS3/E3 Interface Typehttp:/www.ietf.org/rfc/rfc3986.txtIETF RFC 4291, IP Version 6 Addressing Architecturehttp:/www.ietf.org/rfc/rfc4291.txtIETF RFC 4346, The Transport Layer Security (TLS) Protocol Version 1.1http:/www.ietf.org/rfc/rfc4346.txtIETF RFC 4514, Lightwe
39、ight Directory Access Protocol (LDAP): String Representation of Distinguished Nameshttp:/www.ietf.org/rfc/rfc4514.txt2.5 References under developmentThe following documents (and their web addresses) are subject to change.DMTF DSP0200 CIM Operations over HTTP 1.2http:/www.dmtf.org/standards/published
40、_documents/DSP200.pdfDMTF DSP0201, Representation of CIM in XML 2.2http:/www.dmtf.org/standards/wbem/DSP201.htmlDMTF DSP0225, URI Format for DMTF Published XML Schemahttp:/www.dmtf.org/standards/published_documents/DSP0225.pdfDMTF DSP0226, WS-Management Protocol SpecificationDMTF DSP0230, WS-CIM Map
41、ping SpecificationINCITS 388.2, Information Technology Storage Management Technical Specification Part 2: Common Profiles2.6 Other referencesIETF RFC 1945 Hypertext Transfer Protocol - HTTP/1.0 http:/www.ietf.org/rfc/rfc1945.txtIETF RFC 2614 An API for Service Locationhttp:/www.ietf.org/rfc/rfc2614.
42、txtNormative references INCITS 388.1-20115SSL 3.0 Draft SpecificationUML (Universal Modeling Language) Specificationshttp:/www.omg.org/technology/documents/modeling_spec_catalog.htm#UMLITU-T Recommendation X.509 (1997 E): Information Technology - Open Systems Interconnection - The Directory:Authenti
43、cation FrameworkPKCS #12, Personal Information Exchange Syntaxhttp:/ 388.1-2011 Normative references6Definitions, symbols, abbreviations, and conventions INCITS 388.1-20117Clause 3: Definitions, symbols, abbreviations, and conventions3.1 Definitions3.1.1 agentAn Object Manager that includes the prov
44、ider service for a limited set of resources. An Agent may be embedded orhosted and can be an aggregator for multiple devices.3.1.2 aggregationA strong form of an association. For example, the containment relationship between a system and the componentsthat make up the system can be called an aggrega
45、tion. An aggregation is expressed as a Qualifier on theassociation class. Aggregation often implies, but does not require, that the aggregated objects have mutualdependencies.3.1.3 CIM ServerA Server that provides support for CIM requests and provides CIM responses. 3.1.4 Common Information Model (C
46、IM)An object-oriented description of the entities and relationships in a business management environment maintainedby the Distributed Management Task Force. CIM is divided into a Core Model and Common Models. The CoreModel addresses high-level concepts (such as systems and devices), as well as funda
47、mental relationships (suchas dependencies). The Common Models describe specific problem domains such as computer system, network,user or device management. The Common Models are subclasses of the Core Model and may also be subclassesof each other.3.1.5 clientA process that issues requests for servic
48、e. Formulating and issuing requests may involve multiple client processesdistributed over one or more computer systems.3.1.6 dedicated SMI-S ServerA CIM Server that is dedicated to supporting a single device or subsystem. 3.1.7 dynamic host control protocol (DHCP)An Internet protocol that allows nod
49、es to dynamically acquire (“lease”) network addresses for periods of time ratherthan having to pre-configure them.3.1.8 discoveryDiscovery provides information about what physical and logical storage entities have been found within themanagement domain.3.1.9 Distributed Management Task Force (DMTF)An industry organization that develops management standards for computer system and enterprise environments.DMTF standards include WBEM, CIM, DMI, DE
