SMTP服务器管理命令行协议规范

版权申诉

103 浏览量更新于2024-07-19 收藏 1.51MB PDF 举报

"Server Management Command Line Protocol (SMTP) v1.0.pdf" SMTP，即简单邮件传输协议（Simple Mail Transfer Protocol），通常被误解为用于服务器管理的协议，但实际上它主要设计用于在互联网上发送电子邮件。然而，这里的“Server Management Command Line Protocol”并不是指传统的SMTP，而是一种特定的管理协议，由DMTF（Distributed Management Task Force）定义，用以规范服务器的命令行管理。 DMTF是一个专注于推动企业级和系统管理以及互操作性的非营利行业联盟。他们发布了SMASH（System Management Architecture for Server Hardware）系列标准，旨在提高数据中心硬件的管理和自动化。DSP0214文档是这个系列的一部分，详细描述了Server Management CommandLine Protocol（SMCLP）版本1.0，这是一个预发布标准，发布于2005年6月7日。 SMCLP旨在提供一种通过命令行接口来远程管理和控制服务器的机制，这可能包括硬件状态查询、配置更改、故障排查等功能。通过这种协议，管理员可以使用统一的命令语法和结构，实现跨不同厂商硬件的标准化管理，提高效率和互操作性。该文档内容可能涵盖了协议的结构、命令格式、错误处理、安全性考虑、实施指南等多个方面。DMTF允许其成员和非成员复制这些规格文档，只要符合规定用途并给予正确归属。但需要注意的是，DMTF对标准中可能涉及的第三方专利权不做任何表示或承担责任，这意味着实现该标准可能需要考虑潜在的专利许可问题。 SMTP v1.0作为Server Management Command Line Protocol，是DMTF为了提升服务器管理效率和标准化而制定的一个规范，与电子邮件的SMTP协议不同，它专门针对服务器管理任务设计，且可能存在与第三方专利权相关的法律问题。

DSP0214 Server Management Command Line Protocol Specification (SM CLP)

June 7th, 2005 Page 16 of 241

2 SM CLP Overview

This section contains an overview of the Command Line Protocol (CLP). This includes the goals

behind creating the CLP and the specific problems which it attempts to resolve. In addition, this

section will lay the groundwork for the sections that follow by detailing the background and

assumptions of the CLP. This includes the architecture assumed in the design of the CLP and the

components within that architecture.

2.1 Problem Statement

The fundamental problem which is the impetus behind this specification is the growing need to

rely on multi-vendor, out-of-band hardware and software management solutions as core

components of interoperable, heterogeneous enterprise-wide management solution. By the

extending the DMTF Specifications to include a CIM-based command line protocol for

managing out-of-band and out-of-service devices, the DMTF comes closer to realizing it's vision

of enabling end-to-end, multi-vendor interoperability in management systems.

2.2 Principal Goals

The principal goal of this specification is to define a light-weight, human-oriented command line

protocol which is also suitable for scripting environments. This includes a direct mapping to a

subset of the CIM Schema. The command line protocol will specify the syntax and semantics

used to allow the manipulation of the Managed Elements within servers, as collections or

individually.

2.3 Solution

The solution proposed in this document is a command line protocol (CLP), which is transmitted

and received over a text message-based transport protocol. The CLP is defined as a character-

based message protocol and not as an interface, in a fashion similar to SMTP RFC 2821 [23].

The CLP is a command/response protocol, which means that a text command message is

transmitted from the Client over the transport protocol to the Manageability Access Point

(MAP). The MAP receives the command and processes it. A text response message is then

transmitted from the MAP back to the Client.

The CLP is designed to work over existing character oriented transports. The specification

contains mappings to Telnet and SSHv2, but any transport capable of carrying

command/response message data of the type specified herein may be suitable for use as a

transport.

The CLP enables internationalization by providing a mechanism for the Client to indicate to the

MAP the language desired by the Client. Provided the MAP supports the requested language,

output data will be presented to the user with the appropriate translations. This version of the

CLP does not support specific internationalization of user account names and passwords as they

are NOT REQUIRED to be in any specific language. In addition, the CLP input (commands &

syntax) is not translated since CLP syntax is itself its own language.

The CLP allows for extensibility through four different mechanisms: verbs, targets, target

properties, and option names and option arguments. The conventions contained herein allow for

Server Management Command Line Protocol Specification (SM CLP) DSP0214

Page 17 of 241 June 7th, 2005

implementers to extend the interface in a non-conflicting mechanism that allows for

differentiation and experimentation without encroaching upon the standard CLP syntax and

semantics.

2.3.1 General Syntax

The general syntax for the CLP is of the form:

<verb> [<options>] [<target>] [<properties>]

The verb term refers to the specific command or action taking place. These are covered in

detail in Section 4. The list of verbs includes those that establish and retrieve data (“set” and

“show”), create and remove records or instances, (“create” and “delete”), change the state

of a given target (“reset”, “start”, “stop”), manage the current session (“cd”,

“version”, and “exit”) and provide command information (“help”).

The target term indicates the address or path of the target of the command. The format of this

term is discussed in the SM Managed Element Addressing Specification

[4]

. This term can be an

individual Managed Element, such as a disk, a NIC, the MAP itself, or even a service, such as

the transport. This term can also be a collection of Managed Elements supported by the MAP,

such as a system. There can be only one target term specified per command.

Command options always modify the action or behavior of the verb. Options MAY appear

immediately after the verb on the Command Line and MUST be preceded by a hyphen (“-“).

They provide features such as changing the output format, allowing the command to apply to

nested levels, requesting the version of the command be displayed, and requesting help. Note

that there MAY be zero or more option terms per command. For more information, see Section

Command target properties are attributes which may contain values associated with a target that

are needed to process the command. Command target properties identify properties of the

target’s class which are to be retrieved or modified by the command. Valid command target

property names are documented in the MOF file which defines the class. Implementations

MUST use the property name defined in the MOF file to identify the property of the class.

The properties themselves are manipulated with the commands in

Section 4

. If a value is to be

assigned to a property, the syntax MUST be of the form “<property name>=<value>”. There

MAY be zero or more property terms per command.

2.3.2 Architectural Assumptions

There is an underlying assumption that the architecture the CLP is built upon, or is an interface

into, is a CIM Server implementation. The CLP is organized around management tasks mapped

to operations on CIM instances. It does this by retrieving or changing properties and invoking

methods established in instances of the CIM Schema. The mapping of CLP commands to CIM

elements is documented in the CLP-to-CIM Mapping Specification

[13]

to aid implementers and

consumers of this specification.

The CLP consists of a set of specific functions intended for operational control of the server

hardware and rudimentary control of the operating system. It is not intended to be a complete

interface into managing the operating system. Therefore, the CLP contains the commands

DSP0214 Server Management Command Line Protocol Specification (SM CLP)

June 7th, 2005 Page 18 of 241

necessary to operate on a proper subset of the CIM Schema as defined in the CLP-to-CIM

Mapping Specification

[13]

The CLP is also architected to work over existing transports. It is assumed that the transports

will provide the authentication and encryption necessary for the protocol. Role-based command

use authorization is included in the CLP, but the architecture assumes that the CLP relies on the

underlying transport for any access security and authentication. The CLP architecture is

documented in SM Architecture White Paper [3] .

2.4 Architectural Concepts of the SM CLP

The following sections describe some of the key concepts of the SM CLP. A detailed statement

of the architecture of the SM CLP is available in the SM Architecture White Paper [3] .

2.4.1 Physical Connection

The physical connection and media between the Client and the MAP are outside the scope of this

specification. Any physical connection which is capable of running one of the supported

transports should be able to support the CLP. Since the supported transports themselves can run

over IP, it is safe to assume that the CLP can be transmitted and received over any media or

physical connection that supports IP. However, this does not limit support for the CLP to

physical media or connections which support IP. In fact, it is reasonable for an implementation

to be created where the protocol never leaves the managed server.

2.4.2 Transport Management

This specification includes sections detailing the mapping of the CLP over two transport

protocols: Telnet and SSHv2. The CLP is designed to be transport independent, but mappings to

transports other than these two are outside of this specification.

The Client is the terminus of one end of the connection; the CLP Service implementation is the

other. CLP Service implementations MUST manage the transport and the sessions which occur

over the transport.

2.4.3 Authentication, Authorization & Encryption

The CLP Service does not perform any authentication or encryption. It relies entirely upon the

transport to perform these functions. Session transport requirements are documented in Section

6.3.

To accommodate a single basis for user authorization, the user account database required by the

transport is expected to share the user information with the CLP Service once the user is logged

in. For more information, see Section

6.3.

The CLP Service authorizes commands through the use of authorization groups. Each user

account is a member of a group, which MUST be assigned when the account is created. For

more information, see Section

6.1.

The CLP contains commands for the creation, removal and modification of user accounts,

including authorization and access rights. For more information, see Section 4.

Server Management Command Line Protocol Specification (SM CLP) DSP0214

Page 19 of 241 June 7th, 2005

2.4.4 Sessions

Sessions between a Client and a CLP Service are established over a transport protocol. Once the

session has been authenticated, the Client can begin to submit commands using the CLP Service.

Each session has a unique context within the MAP. Within this context, the CLP Service keeps

track of session characteristics. Implementations supporting the CLP MUST maintain a session

context to track session characteristics. Examples of these characteristics include the current

default command target, currently selected output mode, current output language, and the current

user and session identifier. There are commands for manipulating the session characteristics

included in the CLP. For more information, see Section 6.2.1.

2.4.5 Input Editing

The CLP is a command / response protocol. CLP implementations MUST receive and parse an

entire Command Line, complete with verb, target, options and properties. The CLP Service

MUST NOT allow any interactive input or data editing. This does not preclude a Vendor from

providing such capability associated with the Client implementation, but any such capability is

outside of the scope of the specification.

2.4.6 Command Line Protocol Service

The CLP Service is responsible for providing and enforcing the syntax and semantics of the

CLP. Implementations of the CLP service MUST support being configured using the CLP and

MAY support configuration through other interfaces This includes starting, stopping and

changing the attributes of the service.

2.4.6.1 CLP Service Access Point

The transport session is established to the Command Line Protocol Service Access Point. The

access point represents the physical and logical communication mechanism through which the

CLP Service receives incoming connection requests. The CLP provides the mechanisms

necessary to enable, disable and configure the Access Point. If the CLP Service Access Point is

instantiated using an Ethernet NIC, the SSHv2 protocol and the supporting protocol stacks, the

CLP implementation MUST provide mechanisms for configuring the NIC, TCP, IP and SSHv2.

2.4.6.2 Operation Management

All commands submitted through the CLP Service create jobs within the MAP. There is one and

only one global job queue within the MAP. Implementations MUST track all jobs using this

single job queue.

Operations follow the CIM_Job schema, as defined in later sections. The CLP supports

commands to query jobs, retrieve the interim status of jobs, retrieve the final status of jobs, and

delete jobs. Operations are covered further in Section 3.1.6.

2.5 Use Cases

This section describes the intended features, functions and uses of the CLP. Note that the CLP is

not limited to these functions, but these are the specific uses for which the CLP was intended.

DSP0214 Server Management Command Line Protocol Specification (SM CLP)

June 7th, 2005 Page 20 of 241

The CLP is designed to apply to a number of server topologies. This includes, but is not limited

to, stand alone servers, rack mounted servers, blades, partitioned servers & Telco servers. It is

also suitable to manage any necessary enterprise components, enclosures, chassis, racks and

power supplies necessary to utilize servers.

The CLP provides the ability to enumerate and configure server hardware. This includes

discovery of the current hardware configuration and properties, system settings and local IO

devices. The CLP provides some amount of configuration for local disk drives, including local

arrays. The intention of providing this support is to allow initial logical unit creation for

installation and/or provisioning. It is not intended that the CLP Service be the primary interface

for managing mass storage, since these standards and access points exist in the industry.

The CLP also includes the ability to select, control and initiate the transfer of images. This is

provided through the CIM_SoftwareInstallationService as well as the ability to

control the boot configuration of any supported server. In addition, support for heartbeat and

operating system status information is included.

Server state control is included in the CLP. This includes power control, intervention capability

(to halt, reset or shutdown a server) and mechanisms to initiate a dump of the operating system.

Access to some system resources is included in the CLP as well. This includes access and

manipulation of any accessible logs, the ability to view and set remote status displays, LED s and

alarms, the ability to configure alert destinations and the ability to initiate a session with a remote

text-based console device.

The CLP also supports normal expected user session functions such as help, version information

and the ability to exit or terminate a session.

2.6 Known Limitations

First and foremost, while CLP commands are mapped to CIM methods and operations, the CLP

is not intended to be a complete mapping to every CIM method, property and/or operation. The

CLP supports a sufficient subset of CIM Server features to enable the CLP to be the primary

locus of interaction for server management, regardless of server type, physical connection or

operating system state.

Another known limitation pertains to the intended Client. The CLP is primarily focused on an

interactive experience with a human user or simple script. It is not intended to be the primary

interface for advanced server management software to utilize in order to manage their hardware.

Consequently, the format of the commands and their responses as well as the CIM methods,

properties and operations supported may not be sufficient for the CLP Service Access Point to be

the primary interface for advanced server management software.

2.6.1 Scope

The following subjects are within the scope of this document:

– Command Line Protocol syntax and semantics

– input format and output format

– accessing and traversing the target address space

– error handling and semantics

剩余240页未读，继续阅读

Jimbo_Zhang

粉丝: 155
资源: 44

SMTP服务器管理命令行协议规范

System_Control_and_Management_Interface_v1.0.pdf

SQL_Server_2005_Handout_v1.0.pdf

客户关系管理系统v1.0.zip

intelligent chassis management bus bridge specification v1.0

itil 4_中文版_中英文对照版_by iceblue_v1.2.pdf

management.endpoints.web.exposure.include

management.endpoints.web.exposure.include=*

java -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=127.0.0.1 -jar httpUtil.jar

sql server management studio安装失败

最新资源