DASH----Desktop and mobile Architecture for System Hardware----桌面和移动系统硬件架构(DASH)计划

http://baike.baidu.com/subview/813787/11301142.htm

http://sites.amd.com/cn/business/it-solutions/manageability/Pages/manageability.aspx

本词条介绍的是DASH（关于远程管理的一种解决方案），更多含义，请参阅DASH（多义词）。

 

目 录

1DASH简介

2DASH带外管理功能

3DASH给管理员带来的好处

4DASH的几种特殊用途

 

 

1DASH简介

DASH是由DMTF开发的一套规范，旨在为桌面和移动客户端系统提供开放的基于标准的Web服务管理。DASH是一个综合性框架，它提供了新一代标准，以便保护多供应商、分布式企业环境中桌面和移动系统的带外及远程管理的安全。DASH在整个产品系列（传统的桌面系统、移动和膝上型计算机、刀片PC以及瘦客户端）使用相同的工具、语法、语义和接口。[1]

2DASH带外管理功能

DASH允许实施安全可靠的带外管理。DASH 1.1包括下列带外管理功能：

• 安全传输 - 使用HTTPS确保操作的安全性
• 基于SOAP的管理协议 - 使用WS-Management
• 标准网络发现 - 使用RMCP(远程管理和控制协议)和WS-Identify的两阶段发现
• 用户管理 - 提供了一个标准界面，远程控制台可以在这个界面上添加/删除用户、设置/更改密码以及将角色指派给用户。预定义的角色有Admin、operator和read-only。
• 远程电源控制 - 允许在远程启动、关闭、重启或重置PC
• 引导控制 - 指导系统在指定的引导设备（例如PXE、软盘和远程介质）上重启。
• 硬件资产清单- 显示平台型号、CPU版本、BIOS版本、内存和其他硬件信息
• 传感器界面 - 包括显示风扇速度、风扇状态、温度、电源状态和机箱防盗的可选传感器界面
• 平台警报 - 控制台可以通过WS-eventing协议订阅警报。平台警报可能包括温度警报、风扇故障、机箱防盗、ProcHot、ThermTrip和BIOS引导故障
• 文本控制台重定向 - 在BIOS的帮助下，在引导系统、设置BIOS或运行诊断程序期间进行控制台和键盘重定向；在引导期间，操作系统一旦接管任务，文本重定向便告终止
• 介质重定向 - 提供一个从远程设备或映像文件读取数据的“虚拟”CDROM/软盘/磁盘设备。这允许从远程磁盘/CDROM/软件映像引导BIOS。主要用途包括：
• 远程引导到部署操作系统（如WinPE）来启动正式系统
• 远程引导到网络光盘映像来更新BIOS或固件，或运行诊断程序
• 操作系统状态 - 提供带外接口，用于读取操作系统状态（关闭、启动、待机/休眠），或请求改变状态（例如关闭或休眠）
• 不透明数据邮箱 - 允许PC上的软件代理在DASH管理控制器上存储数据，这样，无论后来操作系统或PC电源处于何种状态，远程控制台或远程应用程序都可以读取现成的数据。[1]

3DASH给管理员带来的好处

符合DASH标准的管理工具或控制台可以按一致的供应商中立方式监视和控制DASH客户端系统。这意味着多个不同的客户端可以采用同一种方式完成常见的管理任务。DASH的核心功能缩短了管理员的学习周期，为管理任务提供了灵活性，降低了系统复杂性，并且有助于降低成本。[1]

 

4DASH的几种特殊用途

• 远程电源控制、引导控制和控制台重定向 - 管理员可以通过远程管理控制台对某个客户端系统进行关闭、打开或者重新启动。他们可能想关闭系统以减少能源消耗，或者想打开系统，安装一个补丁然后再关闭。
• 远程诊断 - 帮助台操作员或者管理员可以远程启动一个客户端系统并将一系列输出重定向到远程控制台，在远程位置诊断问题。然后，他们就可以从诊断盘或者设备引导系统，进行远程故障排除。
• 发现 - 管理员可以从管理控制台中自动发现他们可以用DASH管理的客户端系统。然后就能够以一种标准方式查询被管理的客户端。控制台还可以判断某个客户端是否支持DASH，以及可以访问哪些特殊功能或特性。
• 资产清单- 管理员可以从他们的管理工具或者控制台查看客户端系统中的硬件和软件清单。例如，管理员可以检查诸如内存或者硬盘的硬件组件配置，或者查看安装的软件和版本。无论客户端系统处于打开还是关闭状态，都可以查看此清单。
• 远程系统状态监视- 管理员可以远程监视系统中硬件组件的状态，例如温度、机箱防盗以及风扇运行状况。

http://en.wikipedia.org/wiki/Desktop_and_mobile_Architecture_for_System_Hardware

Desktop and mobile Architecture for System Hardware

From Wikipedia, the free encyclopedia

 

 

DASH ("Desktop and mobile Architecture for System Hardware") is a DMTF standard on requirements for implementing the Desktop and Mobile Architecture for System Hardware.

DASH implementation requirements specification (DSP0232) was launched by the Desktop and Mobile Working Group (DMWG) of the DMTF in April 2007. The current version, DASH 1.1, was published in December 2007 and became a DMTF standard in June 2009.

In-service and out-of-service systems can be managed, with manageability aligned between the modes, independent of operating system state. Both HTTP and HTTPSmanagement ports are supported: TCP ports 623 and 664, respectively, for connections from remote management consoles to DASH out-of-band management access points (MAP).

The DMTF CIM schema defines the supported DASH management data and operations. There are currently 28 CIM profiles supported in the DASH 1.1 specification.

DASH uses the DMTF's Web Services for Management (WS-Management) protocol for communication of CIM objects and services.

The web services expose a common set of operations for system management:

• DISCOVER
• GET, PUT, CREATE and DELETE management resources, such as property values & settings
• ENUMERATE for tables and collections
• SUBSCRIBE to and DELETE events (indication delivery)
• EXECUTE for services (method invocation)

Contents

[hide] 

• 1 DASH management access point discovery
• 2 DASH protocol stack
• 3 DASH profiles
• 4 See also
• 5 References
• 6 External links

DASH management access point discovery[edit]

Discovery of access points is a two phase process:

• Phase 1: an RMCP Presence Ping request is sent (broadcast, multicast or unicast) and an RMCP Presence Pong response is received indicating support for WS-Management.
• Phase 2: a WS-Management "Identify" request is sent and response is received indicating support for DASH, which version, and which security profiles.

DASH protocol stack[edit]

The layered DASH management protocol stack:

Layer	Type
DASH Management Service	App
DASH CIM Profiles	App
WS-Management CIM Binding	App
Data Transfer (WS-Eventing, WS-Enum, WS-Transfer, WS-Addressing)	WS Layer
Security Profiles	WS Layer
Simple Object Access Protocol (SOAP) / XML	SOAP
HTTP/TLS	SOAP
TCP	SOAP
IP	Network
MAC/PHY	Network

DASH profiles[edit]

The DMTF CIM Profiles supported by the DASH 1.1 specification:^[1]

Profile	Support
Base Desktop and Mobile	Mandatory
Profile Registration	Mandatory
Role Based Authorization	Mandatory
Simple Identity Management	Mandatory
Battery	Optional
BIOS Management	Optional
Boot Control	Optional
CPU	Optional
DHCP Client	Optional
DNS Client	Optional
Ethernet Port	Optional
Fan	Optional
Host LAN Network Port	Optional
Indications	Optional
IP Interface	Optional
KVM Redirection	Optional
Media Redirection	Optional
Opaque Management Data	Optional
OS Status	Optional
Physical Asset	Optional
Power State Management	Optional
Power Supply	Optional
Sensors	Optional
Software Inventory	Optional
Software Update	Optional
System Memory	Optional
Text Console Redirection	Optional
USB Redirection	Optional

As DASH is designed for desktop and mobile computer systems, a related DMTF standard for management of server computer systems also exists: Systems Management Architecture for Server Hardware (SMASH), with a similar set of CIM Profiles.

Intel Active Management Technology (AMT) is a compliant implementation of DASH.

See also[edit]

• Common Information Model (CIM)
• WS-Management
• Systems Management Architecture for Server Hardware (SMASH)
• Alert Standard Format (ASF)
• Alert on LAN
• Wake-on-LAN (WOL)
• IPMI -A server management interface standard covering similar functionality as DASH, but using a UDP-based protocol compared with the TCP/SOAP protocol of DASH. DASH can be implemented on top of IPMI.

References[edit]

1. Jump up^ "DASH Implementation Requirements"

External links[edit]

• DMTF DASH Initiative
• DMTF DASH Specifications and Technical Information
• DMTF DASH Technical Note (2007)
• DMTF DASH Press Release (2007)
• DASH 1.1 Implementation Requirements
• DASH 1.1 White Paper

Standards of DMTF
DMTF standards	ASF CDM CIM DASH DMI NC-SI SMASH SMBIOS WBEM WS-Management
Related standards	CMPI JSR-48 OVF SMI-S
Implementations	WMI OMI WQL

http://www.dmtf.org/standards/dash

Desktop and Mobile Architecture for System Hardware

DMTF’s Desktop and mobile Architecture for System Hardware (DASH) Standard is a suite of specifications that takes full advantage of DMTF’s Web Services for Management (WS-Management) specification – delivering standards-based Web services management for desktop and mobile client systems. Through DASH, DMTF provides the next generation of standards for secure out-of-band and remote management of desktop and mobile systems.

The System Management Forum, part of DMTF's Interoperability Committee, develops and implements programs for verifying compliance of software and hardware that implement DMTF system management standards.

DMTF welcomes feedback on our standards, but requires that individuals submitting comments first agree to ourFeedback Policy.

Note: All relevant profiles are available on this aggregated Management Profiles page.

DASH 1.1 Features and Benefits

NEW FEATURE	BENEFIT
KVM (Keyboard, Video and Mouse) and text console redirection support	Provides the capability to manage KVM and text console redirections provided by the system.
USB and media redirection support	Provides the capability to manage USB and media redirections provided by the system.
BIOS (Basic Input Output System) Management	Provides the capability to remotely change BIOS settings.
NIC (Network Interface Card) Management	Provides management of MAC and IP addresses, DNS and DHCP configuration. Adds the capability to represent and manage a network port that provides a LAN interface and its associated controller.
Operating System Status	Enables representation of OS name/version and OS status.
Opaque Data Management (offline mailbox)	Enables manageability of data storage that can be used by management applications in band and out of band.
Software Update	Provides management interfaces for updating firmware and software.
Battery Management	Provides the capability to represent and manage batteries.

DMTF Specifications

DSP #	Version	Title	Date	Comments
DSP0232	1.1.0	DASH Implementation Requirements	22 Jun 2009	.pdf file, DMTF Standard
DSP0232	1.0.1	DASH Implementation Requirements	16 Oct 2009	.pdf file, DMTF Standard
DSP0232	1.0.0	DASH Implementation Requirements	19 May 2009	.pdf file, DMTF Standard

DMTF Profiles

DSP #	Version	Title	Date	Comments
DSP1116	1.0.0	IP Configuration Profile	4 Feb 2013	.pdf file. DMTF Standard
DSP1108	1.0.0	Physical Computer System View Profile	30 Aug 2013	.pdf file. DMTF Standard
DSP1074	1.0.1	Indicator LED Profile Specification	3 Apr 2013	.pdf file. DMTF Standard
DSP1052	1.0.2	Computer System Profile	4 Feb 2013	.pdf file. DMTF Standard
DSP1029	1.1.0	OS Status Profile	1 Aug 2013	.pdf file. DMTF Standard
DSP1018	1.1.1	Service Processor Profile	3 Apr 2013	.pdf file. DMTF Standard

White Papers and Technical Notes

DSP #	Version	Title	Date	Comments
DSP2014	1.1.0	Systems Management Architecture for Mobile and Desktop Hardware White Paper	15 Dec 2007	.pdf file, DMTF Informational
DSP2014	1.0.0	Systems Management Architecture for Mobile and DesktopHardware White Paper	12 Feb 2007	.pdf file, DMTF Informational
Dash Tech Note:	1.0.0	DASH Delivers Multi-Vendor Management for Desktop and Mobile Systems	16 Mar 2007	.pdf file, DMTF Informational