1、American National StandardDeveloped byfor Information Technology Server ManagementCommand Line Protocol(SM CLP) SpecificationANSI INCITS 438-2008ANSIINCITS438-2008Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permi
2、tted without license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSIINCITS 438-2008American National Standardfor Information Technology Server ManagementComman
3、d Line Protocol(SM CLP) SpecificationSecretariatInformation Technology Industry CouncilApproved January 9, 2008American National Standards Institute, Inc.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted with
4、out license from IHS-,-,-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 ofStandards Review, su
5、bstantial 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 their resolution.Th
6、e 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 American Nation
7、al 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 Standards Instit
8、ute. 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 require that acti
9、on 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 Standards Institute
10、, 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 written permission of ITI, 1250 Eye Street NW, Washin
11、gton, 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 have undertaken a
12、 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 further patent searc
13、h 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.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for
14、ResaleNo reproduction or networking permitted without license from IHS-,-,-iContentsPageForeword . iiiIntroduction .vi1 Scope. 12 Normative References . 13 Terms and Definitions 24 Symbols and Abbreviated Terms. 75 Server Management Command Line Protocol (SM CLP) Specification. 85.1 Semantics 85.2 S
15、yntax 186 SM CLP Verbs . 416.1 Verb Support Requirements 426.2 cd . 436.3 create. 476.4 delete . 516.5 dump 576.6 exit . 636.7 help 656.8 load 676.9 reset. 716.10 set 746.11 show. 826.12 start 1106.13 stop 1136.14 version . 1177 Standard Command Options . 1197.1 General 1197.2 all . 1227.3 destinati
16、on 1227.4 display 1227.5 examine . 1257.6 force. 1267.7 help 1267.8 keep . 126Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iiPage7.9 level . 1277.10 output. 1287.11 source 13
17、37.12 version . 1337.13 wait 1348 SM CLP Session 1348.1 Authentication, Authorization, and Audit 1348.2 CLP Session 1358.3 Transport . 141AnnexesA SM CLP Command Grammar in ABNF Notation (RFC2234) 143B W3C Universal Resource Identifiers (URI) 149C W3C Extensible Markup Language (XML) 150D POSIX Util
18、ity Conventions . 151E Conventions. 153F Notation . 154G Bibliography . 155Tables1 CLP Reserved Characters and Character Sequences 192 Common Output Keywords 273 Command Status Keywords 274 Command Status Values and Tags . 285 Message Keywords . 286 Processing Error Values and Tags 297 Job Error Key
19、words . 308 Error Type Values and Descriptions 309 CIM Status Code Values and Descriptions 3110 Severity Values and Descriptions 3211 Probable Cause Values and Descriptions . 3312 Verb Support Requirements 4213 Data Element Types and all Option . 8414 Standard Command Options . 12015 Verb and Option
20、 Support . 12116 Output Option Arguments 12817 Output Options for Controlling Command Status Output. 133Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iiiPage18 Command Authori
21、zations for CLP Groups. 13519 Telnet Transport Support Requirements 141Figures1 Session Establishment Sequence 1372 Command Interaction Sequences 1383 Session Switching Sequences. 1394 Session Termination Sequences . 140Copyright American National Standards Institute Provided by IHS under license wi
22、th ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ivForeword (This foreword is not part of American National Standard ANSI INCITS 438-2008.)The Server Management Command Line Protocol (SM CLP) Specification(DSP0214) was prepared by the Server Management Worki
23、ng Group. This docu-ment was prepared in accordance with ISO/IEC Directives, Part 2: Rules for thestructure and drafting of International Standards.The Server Management Command Line Protocol (SM CLP) Specification specifies acommon command line syntax and message protocol semantics for managing com
24、-puter resources in Internet, enterprise, and service provider environments.DMTF is a not-for-profit association of industry members dedicated to promoting en-terprise and systems management and interoperability. This standard contains seven annexes. Annex A is normative and is considered partof thi
25、s standard. The other annexes are informative and are not considered part ofthis standard.Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcome. They should be sent to InterNational Committee for InformationTechnology Standards (INCITS), ITI, 1250 Eye St
26、reet, NW, Suite 200, Washington,DC 20005.This standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily imply that all committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing member
27、s:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. Leslie BixelSteve Ziles (Alt.)AIM Global, Inc. Dan MullenCharles Biss (Alt.)Apple Computer, Inc. David MichaelElectronic Industries Alliance . Edward Mikoski, Jr.David Thompson (Al
28、t.)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. SillettiRobert Weir (Alt.)Sandy Block (Alt.)Ric
29、hard Schwerdtfeger (Alt.)IEEE . Judith GormanTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodi Haasz (Alt.)Bob Labelle (Alt.)Intel. Philip WennblomDave Thewlis (Alt.)Jesse Walker (Alt.)Grace Wei (Alt.)Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo
30、reproduction or networking permitted without license from IHS-,-,-vOrganization Represented Name of RepresentativeLexmark InternationalDon WrightDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft CorporationJim HughesDon Stanwyck (Alt.)Isabelle Valet-Harper (Alt.)National Institute of Standards the CLP
31、Service implementa-tion is the other. CLP Service implementations manage the transport and the ses-sions that occur over the transport as required by DSP1005. Authentication, Authorization, and EncryptionThe CLP Service does not perform any authentication or encryption. It relies entirelyon the tran
32、sport to perform these functions. Session transport requirements are doc-umented in 8.3.To accommodate a single basis for user authorization, the user account database re-quired by the transport is expected to share the user information with the CLP Ser-vice once the user is logged in. For more info
33、rmation, see 8.3.The CLP Service authorizes commands through the use of authorization groups.Each CLP User shall be a member of at least one CLP Group. For more information,see 8.1.The CLP contains commands for the creation, removal, and modification of user ac-counts, including authorization and ac
34、cess rights. For more information, see Clause6.SessionsSessions between a Client and a CLP Service are established over a transport proto-col. After the session has been authenticated, the Client can begin to submit com-mands using the CLP Service. Each session has a unique context within the MAP.Wi
35、thin this context, the CLP Service keeps track of session characteristics. Imple-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ixmentations will maintain a session context and
36、 session characteristics as required byDSP1005. Examples of these characteristics include the Current Default Target, cur-rently selected output mode, current output language, and the current user and ses-sion identifier. Commands for manipulating the session characteristics are includedin the CLP.
37、For more information, see 8.2.2.Input EditingThe CLP is a command/response protocol. CLP implementations shall receive andparse an entire Command Line, complete with verb, command target term, options,and properties. The CLP Service shall not allow any interactive input or data editing.This does not
38、 preclude a vendor from providing such capability associated with theClient implementation, but any such capability is outside of the scope of this specifi-cation.Command Line Protocol Service The CLP Service is responsible for providing and enforcing the syntax and semanticsof the CLP. Implementati
39、ons will support being managed as required by DSP1005.This includes starting, stopping, and changing the attributes of the service.CLP Service Access PointThe transport session is established to the CLP Service Access Point (SAP). The ac-cess point represents the physical and logical communication m
40、echanism throughwhich the CLP Service receives incoming connection requests. The CLP providesthe mechanisms necessary to enable, disable, and configure the SAP. Implementa-tions will support managing the supporting protocol stacks as required by DSP1005.Operation ManagementAll commands submitted thr
41、ough the CLP Service create jobs within the MAP. Thereis one and only one global job queue within the MAP. Implementations shall track alljobs using this single job queue. Operations follow the CIM_Job schema, as defined in later sections. The CLP sup-ports commands to query jobs, retrieve the inter
42、im status of jobs, retrieve the finalstatus of jobs, and delete jobs. Operations are covered further in 5.1.6. Use CasesThis section describes the intended features, functions, and uses of the CLP. Notethat the CLP is not limited to these functions, but these are the specific uses for whichthe CLP w
43、as intended.The CLP is designed to apply to a number of server topologies. This includes, but isnot limited to, stand-alone servers, rack-mounted servers, blades, partitioned serv-ers, and Telco servers. It is also suitable to manage any necessary enterprise com-ponents, enclosures, chassis, racks,
44、and power supplies necessary to utilize servers.The CLP provides the ability to enumerate and configure server hardware. This in-cludes discovery of the current hardware configuration and properties, system set-tings, and local IO devices. The CLP provides some amount of configuration for localdisk
45、drives, including local arrays. The intention of providing this support is to allowinitial logical unit creation for installation, provisioning, or both. It is not intended thatthe CLP Service be the primary interface for managing mass storage, because thesestandards and access points exist in the i
46、ndustry.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-xThe CLP also includes the ability to select, control, and initiate the transfer of images.Also provided is the ability t
47、o control the boot configuration of any supported server.In addition, support for heartbeat and operating-system-status information is includ-ed.Server state control is included in the CLP. This includes power control, interventioncapability (to halt, reset, or shut down a server), and mechanisms to
48、 initiate a dumpof the operating system.Access to some system resources is also included in the CLP. This includes accessand manipulation of any accessible logs; the ability to view and set remote status dis-plays, LEDs, and alarms; the ability to configure alert destinations; and the ability toinit
49、iate a session with a remote text-based console device.The CLP also supports normal expected user session functions such as help, versioninformation, and the ability to exit or terminate a session.Known LimitationsFirst and foremost, while CLP commands are mapped to CIM methods and opera-tions, the CLP i
