Users Guide

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, a notification may not be available, but the
server is reset as if the power switch was activated. ASR is implemented using a 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.
You can perform automatic system recovery operations such as reboot, power cycle, or power off the server after a specified time
interval. This feature is enabled only if the operating system watchdog timer is disabled. If OpenManage Server Administrator is installed,
this monitoring feature is disabled to avoid duplicate watchdog timers.
Windows Management Instrumentation providers
WMI is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented
components provide information and notification. WMI is Microsoft's implementation of the Web-Based Enterprise Management (WBEM)
and Common Information Model (CIM) standards from the Distributed Management Task Force (DMTF) to manage Server hardware,
operating systems and applications. WMI Providers helps to integrate with Systems Management Consoles such as Microsoft System
Center and enables scripting to manage Microsoft Windows Servers.
You can enable or disable the WMI option in iDRAC. iDRAC exposes the WMI classes through the iDRAC Service Module providing the
server’s health information. By default, WMI information feature is enabled. The iDRAC Service Module exposes the WSMan monitored
classes in iDRAC through WMI. The classes are exposed in the
root/cimv2/dcim namespace.
The classes can be accessed using any of the standard WMI client interfaces. For more information, see the profile documents.
The following examples use the DCIM_account class to illustrate the capability that WMI information feature provides in iDRAC Service
Module. For the details of the supported classes and profiles, see the WSMan profiles documentation available at www.dell.com/support.
Table 49. Examples of DCIM_account class
CIM Interface WinRM WMIC PowerShell
Enumerate instances of a
class
winrm e wmi/root/
cimv2/dcim/
dcim_account
wmic /namespace:\
\root\cimv2\dcim
PATH dcim_account
Get-WmiObject
dcim_account -
namespace root/
cimv2/dcim
Get a specific instance of a
class
winrm g wmi/root/
cimv2/dcim/
DCIM_Account?
CreationClassName=DC
IM_Account
+Name=iDRAC.Embedded
.1#Users.2+SystemCre
ationClassName=DCIM_
SPComputerSystem
+SystemName=systemmc
wmic /namespace:\
\root\cimv2\dcim
PATH dcim_account
where
Name="iDRAC.Embedded
.1#Users.16"
Get-WmiObject -
Namespace root
\cimv2\dcim -Class
dcim_account -
filter
"Name='iDRAC.Embedde
d.1#Users.16'"
238 Using iDRAC Service Module