As more and more management functionalities are being added into iDRAC (Service Processor), there is a lesser and lesser need for fat proprietary agents to be running in the Operating Systems to enable system management/monitoring. In pursuit of this idea, multiple management capabilities are pushed to iDRAC and Dell has started working on enabling system management with thinner and thinner agents in the OS. describes some of these initiatives and one of them is Wsman Request redirection.

Recently a new plugin was pushed to openwsman which enables the redirection of wsman requests from the host to iDRAC(or any remote wsman server). Essentially, the openwsman service running in the host will act as a proxy, filters the incoming requests based on the ResourceUri and forwards the right requests to iDRAC. The host's openwsman daemon (the proxy) eventually captures the response from iDRAC(or the remote server) and forwards the same to primary client. This setup will enable system management and monitoring without having to install any proprietary management agents in the OSes.

NOTE: the redirection plugin is only available in 2.3.6 and higher versions of openwsman.


To enable the WSMAN request redirection to idrac, the following section has to be added to openwsman.conf file:


#mandatory fields








#optional Fields

#default is /wsman


#default is basic


#default is root/cimv2


#default is 0


#default is 0


#default is NULL


#default is NULL



With the above configuraiton section added to opewsman.conf any WSMAN requests coming to the host with ResourceURI* will be redirected to iDRAC and all the other requests will be handled by one of the other openwsman plugins in the host. In the above example is the ip address of iDRAC, listening at port 443.

iDRAC has SSL enabled by default. So, the server's identify certificate has to be provided to the redirect plugin. Please note, even in the case noverifypeer is set to 1 (where the servercert is not verified), a dummy cert has to be provided in the redirect section. For production servers, it is always recommended to have noverifypeer=0 and noverifyhost=0.


The username and password values will be imported from the primary wsman request if none are provided in the redirect. The rest of the values pick up default values as shown above configuraiton. Now an example:


wsman enumerate -h host_ip -V -v -c dummy.cert -P 5986 -u root -p password -y -O out

NOTE: The username, password, cert provided in the primary wsman command are to autheticate to the host. The details captured in the openwsman.conf file are to authenticate to iDRAC.


Sending the above request to a host, output similar to the following will be noticed:

<?xml version="1.0" encoding="UTF-8"?>

<s:Envelope xmlns:s="" xmlns:wsa="" xmlns:wsman="" xmlns:wsen="" xmlns:n1="">







































The wsman redirection works with the standard Actions like enumerate, get, put, create, delete and invoke. The requests for associations on iDRAC CANNOT be redirected. Also, redirection for WSMAN indications is not enabled yet.


On a side note, OpenLMI( ) is an initiative to provide common infrastructure to enable Management & monitoring of Linux Systems. This project provides low level interfaces to hardware and software management and monitoring in the form of CIMOM providers. The targets of this effort are the in-band components like Services, Network, Storage, etc. After registering these providers to a CIMOM they can be accessed via WSMAN too.

Having the wsman redirection enabled (to iDRAC) and openlmi providers registered, will enable the Admins to have a single interface for managing both in-band and out-of-band components via WSMAN.