Jump to content

Desktop and mobile Architecture for System Hardware

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Dkoper (talk | contribs) at 00:29, 5 December 2014 (added infobox). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Desktop and Mobile Architecture for System Hardware
AbbreviationDASH
StatusPublished
Year started2007
Latest version1.1
June 2009
OrganizationDistributed Management Task Force
Related standardsWS-Management
DomainSystems management
Websitewww.dmtf.org/standards/dash

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 HTTPS management 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)

DASH management access point discovery

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

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

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

References