Users Guide

● In-band iDRAC SNMP alerts
● View operating system (OS) information
● Replicate Lifecycle Controller logs to operating system logs
● Perform automatic system recovery options
● Populate Windows Management Instrumentation (WMI) Management Providers
● Integrate with SupportAssist Collection. This is applicable only if iDRAC Service Module version 2.0 or later is installed. For
more information, see Generating SupportAssist Collection.
● Prepare to Remove NVMe PCIe SSD. For more information, see Idracug_preparing to remove nvme pcie ssd.
NOTE: The features such as Windows Management Instrumentation Providers, Prepare to Remove NVMe PCIe SDD
through iDRAC, Automating SupportAssist Collection OS collection are supported only on Dell PowerEdge servers with
minimum firmware version 2.00.00.00 or later.
Redfish profile support for network attributes
iDRAC Service Module v2.3 or later provides additional network attributes to iDRAC, which can be obtained through the REST
clients from iDRAC. For more details, see iDRAC Redfish profile support.
Operating system information
The OpenManage Server Administrator currently shares operating system information and host name with iDRAC. The iDRAC
Service Module provides similar information such as OS name, OS version, and Fully Qualified Domain Name (FQDN) with
iDRAC. By default, this monitoring feature is enabled. It is not disabled if OpenManage Server Administrator is installed on the
host OS.
iDRAC Service Module version 2.0 or later has amended the operating system information feature with the OS network
interface Monitoring. When iDRAC Service Module version 2.0 or later is used with iDRAC 2.00.00.00, it starts monitoring the
operating system network interfaces. You can view this information using iDRAC web interface, RACADM, or WSMAN. For more
information, see Viewing network interfaces available on host os.
When iDRAC Service Module version 2.0 or later is used with iDRAC version lower than 2.00.00.00, the OS information feature
does not provide OS network interface monitoring.
Replicate Lifecycle logs to OS log
You can replicate the Lifecycle Controller Logs to the OS logs from the time when the feature is enabled in iDRAC. This is similar
to the System Event Log (SEL) replication performed by OpenManage Server Administrator. All events that have the OS Log
option selected as the target (in the Alerts page, or in the equivalent RACADM or WSMAN interfaces) are replicated in the OS
log using the iDRAC Service Module. The default set of logs to be included in the OS logs is the same as configured for SNMP
alerts or traps.
iDRAC Service Module also logs the events that have occurred when the operating system is not functioning. The OS logging
performed by iDRAC Service Module follows the IETF syslog standards for Linux-based operating systems.
NOTE:
Starting iDRAC Service Module version 2.1, the Lifecycle Controller Logs replication location in the Windows OS logs
can be configured using the iDRAC Service Module installer. You can configure the location while installing iDRAC Service
Module or modifying the iDRAC Service Module installer.
If OpenManage Server Administrator is installed, this monitoring feature is disabled to avoid duplicate SEL entries in the OS log.
NOTE:
On Microsoft Windows, if iSM events get logged under System logs instead of Application logs, restart the Windows
Event Log service or restart the host OS.
Automatic system recovery options
The Automatic system recovery feature is a hardware-based timer. If a hardware failure occurs, the Health Monitor may not
be called, but the server is reset as if the power switch was activated. ASR is implemented using a "heartbeat" timer that
continuously counts down. The Health Monitor frequently reloads the counter to prevent it from counting down to zero. If the
ASR counts down to zero, it is assumed that the operating system has locked up and the system automatically attempts to
reboot.
262
Using iDRAC Service Module