Web Services for Management (WS–MAN) is a Simple Object Access Protocol (SOAP)–based protocol used for systems management. WS–MAN provides an interoperable protocol for devices to share and exchange data across networks. iDRAC6 uses WS–MAN to convey Distributed Management Task Force (DMTF) Common Information Model (CIM)–based management information; the CIM information defines the semantics and information types that can be manipulated in a managed system. The Dell™–embedded server platform management interfaces are organized into profiles, where each profile defines the specific interfaces for a particular management domain or area of functionality. Additionally, Dell has defined a number of model and profile extensions that provide interfaces for additional capabilities.
The data available through WS-MAN is provided by iDRAC6 instrumentation interface mapped to the DMTF profiles and Dell extension profiles.
WS-Management Features
The WS–Management specification promotes interoperability between management applications and managed resources. By identifying a core set of Web service specifications and usage requirements to expose a common set of operations that are central to all systems management, WS–Management has the ability to:
DISCOVER the presence of management resources and navigate between them
GET, SET, CREATE, and DELETE individual management resources, such as settings and dynamic values
ENUMERATE the contents of containers and collections, such as large tables and logs
EXECUTE specific management methods with strongly typed input and output parameters
Supported CIM Profiles
Table 17-1. Supported CIM Profiles
Standard DMTF
Base Server Defines CIM classes for representing the host server.
Base Metrics Defines CIM classes for providing the ability to model and control metrics captured for managed elements.
Service Processor Defines CIM classes for modeling service processors.
USB Redirection Defines CIM classes for describing information about USB redirections. For keyboard, video, and mouse devices, this profile should be used if the devices are to be managed as USB devices.
Physical Asset Defines CIM classes for representing the physical aspect of the managed elements. iDRAC6 uses this profile to represent the host server's and its component's FRU information, as well as the physical topology.
SM CLP Admin Domain Defines CIM classes for representing CLP's configuration. iDRAC6 uses this profile for its own implementation of CLP.
Power State Management Defines CIM classes for power control operations. iDRAC6 uses this profile for the host server's power control operations.
CLP Service Defines CIM classes for representing CLP's configuration. iDRAC6 uses this profile for its own implementation of CLP.
IP Interface Defines CIM classes for representing an IP interface of a managed system.
DHCP Client Defines CIM classes for
representing a DHCP client and its associated capabilities and configuration.
DNS Client Defines CIM classes for
representing a DNS client in a managed system.
Record Log Defines CIM classes for
representing different type of logs. iDRAC6 uses this profile to represent the
System Event Log (SEL) and iDRAC6 RAC Log.
Role Based Authorization Defines CIM classes for representing roles. iDRAC6 uses this profile for configuring iDRAC6 account privileges.
SMASH Collections Defines CIM classes for representing CLP's configuration. iDRAC6 uses this profile for its own implementation of CLP.
Profile Registration Defines CIM classes for advertising the profile implementations. iDRAC6 uses this profile to advertise its own implemented profiles, as described in this table.
Simple Identity Management Defines CIM classes for representing identities. iDRAC6 uses this profile for configuring iDRAC6 accounts.
Ethernet Port Defines CIM classes for representing an Ethernet port, its associated controller, and Ethernet interfaces in a managed system. Associations with the port's physical aspects and profile–implementation version information are modeled in this profile.
Sensor Defines CIM classes used to describe the sensors in a managed system. It also defines association classes that describe the relationship of the sensors with the monitored devices.
Dell Extensions
Active Directory Client Defines CIM and Dell extension classes for configuring iDRAC6 Active Directory client and the local privileges for Active Directory groups.
Virtual Media Defines CIM and Dell extension classes for configuring iDRAC6 Virtual Media. Extends USB Redirection Profile.
OS Deployment Defines CIM and Dell extension classes for representing the configuration of OS Deployment features. It extends the management capability of referencing profiles by adding the capability to support OS deployment activities by manipulating OS Deployment features provided by the service processor.
Software Inventory Defines CIM and Dell Extensions for representing currently installed BIOS, component firmware, Diagnostics, Unified Server Configurator, and Driver Pack versions. Also provides representation of versions of BIOS and firmware update images available in Lifecycle Controller for rollback and re-installation.
Software Update Defines CIM and Dell extensions for representing the service class and methods for updating BIOS, Diagnostics, driver pack, and component and Lifecycle Controller firmware. Update methods support update from CIFS, NFS, FTP, and HTTP network share locations and from update images located in the Lifecycle Controller. Update requests are formulated as jobs and can be scheduled immediately or later with a choice of types of reboot actions to apply the updates.
Job Control Defines CIM and Dell extensions for managing jobs generated by update requests. Jobs can be created, deleted, modified, and aggregated into job queues to sequence and perform multiple updates in a single reboot.
LC Management Defines CIM and Dell extensions for getting and setting attributes for managing Auto-Discovery and Part Replacement Lifecycle Controller features.
iDRAC6 WS–MAN implementation uses SSL on port 443 for transport security, and supports basic and digest authentication. Web services interfaces can be utilized by leveraging client infrastructure such as Windows® WinRM and Powershell CLI, open source utilities like WSMANCLI, and application programming environments like Microsoft® .NET®.
There are additional implementation guides, white papers, profile, and code samples available in the Dell Enterprise Technology Center at www.delltechcenter.com.
