Users Guide

The prerequisite to manage the hardware or the firmware is to have a dedicated connection between a device and the supported iDRAC
interface. Using the iDRAC access via Host OS feature, you can connect to an iDRAC interface from an OS IP or host irrespective of the
connection between a device and an iDRAC dedicated network. This feature allows you to monitor the hardware or firmware even if the
iDRAC is not connected to the servers.
In-band support for iDRAC SNMP alerts
Using iDRAC, an out-of-band server management and monitoring tool, the SNMP traps/alerts can be recorded in the log. However, from
a host OS systems management using in-band agent perspective, the preference is more on the SNMP alert received from the host OS
than the traps received from iDRAC. When an SNMP alert is received from iDRAC, it would be challenging to determine the source of the
alert as it is from an iDRAC IP and not the system IP.
Starting from 14th generation of servers, all events that have the "SNMP Trap" option as the target (in the Alerts page or in the
equivalent RACADM or WSMAN interfaces) can be received as SNMP trap through the OS using the iDRAC Service Module. Starting iSM
3.0.1 or later and iDRAC firmware 3.0.0 or later, this feature does not require iSM LCL replication feature to be enabled. Only the events
logged in the LC log after the iDRAC Service Module was installed are sent as SNMP traps.
Using iDRAC Service Module 2.3 or later, you can receive SNMP alerts from the host OS which is similar to the alerts that are generated
by iDRAC.
NOTE: By default this feature is disabled. Though the In-band SNMP alerting mechanism can coexist along with iDRAC
SNMP alerting mechanism, the recorded logs may have redundant SNMP alerts from both the sources. It is
recommended to either use the in-band or out-of-band option, instead of using both.
NOTE: You can use the In-band SNMP feature on 12th generation of Dell’s PowerEdge Servers or later with a minimum
iDRAC firmware version 2.30.30.30.
Enable WSMAN Remotely
Currently with the WMI information feature, you can connect to the host Microsoft Windows WMI namespace to monitor the system
hardware. The WMI interface on the host is enabled by default and you can access it remotely. However, if you wish to access the WMI
interfaces using WINRM’s WMI adapter, you have to enable it manually as it is not enabled by default. Using this feature, you can access
the WINRM WMI namespaces remotely by enabling it during installation.
This feature can be accessed using PowerShell commands. The commands used are as follows:
Table 7.
Command Description
Enable-iSMWSMANRemote —Status enable —
Forcereconfigure yes —Createselfsigncert yes —
IPAddress <IP address> —Authmode Basic, Kerberos,
Certificate
Enabling and configuring the remote WSMAN feature
Enable-iSMWSMANRemote —Status get
Viewing the status of remote WSMAN feature
Enable-iSMWSMANRemote —Status disable
Disable remote WSMAN feature
Enable-iSMWSMANRemote —Status enable —
Forcereconfigure yes —Createselfsigncert yes —
IPAddress <IP address>
Reconfigure the remote WSMAN feature
NOTE: You must have a server authenticating certificate and a https protocol to work with this feature.
Auto-updating of iDRAC Service Module
Starting from iDRAC Service Module version 3.0.1 you can do the auto-update. It aims at making the update process easier for you, by
integrating iSM update with the iDRAC auto-update process.
NOTE:
If iDRAC auto-update is enabled, iDRAC Service Module LC DUP must be updated to the latest version from
dell.com/support.
iDRAC Service Module monitoring features 27