Users Guide
Table Of Contents
- Dell EMC iDRAC Service Module 4.1.0.0 User’s Guide
- Contents
- Introduction
- Preinstallation setup
- Installing iDRAC Service Module
- Initial installation of iDRAC Service Module through iDRAC Enterprise or Datacenter or iDRAC Express on Microsoft Windows and Linux
- Installing iDRAC Service Module on Microsoft Windows operating systems
- Silent installation of iDRAC Service Module on Microsoft Windows
- Modifying iDRAC Service Module components on Microsoft Windows operating systems
- Repairing iDRAC Service Module running on Microsoft Windows operating systems
- Uninstalling iDRAC Service Module running on Microsoft Windows operating systems
- Installing the iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module on supported Linux operating systems
- Installing iDRAC Service Module when System Configuration Lock Down Mode is enabled in iDRAC
- Configuring iDRAC Servcie Module
- Security configurations and compatibility
- iSM monitoring features
- S.M.A.R.T monitoring
- Operating system information
- Lifecycle Controller log replication into operating system
- Automatic system recovery
- Windows Management Instrumentation Providers
- Prepare to remove a NVMe PCIe SSD device
- Remote iDRAC hard reset
- iDRAC access via Host OS
- Accessing iDRAC via GUI, WS-Man, Redfish, and Remote RACADM
- In-Band support for iDRAC SNMP alerts
- Mapping iDRAC Lifecycle Logs to OMSA and OMSS SNMP alerts
- Enable WS-Man remotely
- Autoupdating iSM
- FullPowerCycle
- SupportAssist on the box
- Configuring the In-Band SNMP Get feature—Linux
- Configuring the In-Band SNMP Get feature—Windows
- iDRAC GUI Launcher
- Single sign-on to iDRAC UI from host operating system administrators desktop
- IPv6 communication between iSM and iDRAC over OS-BMC Pass-thru
- Frequently asked questions
- Linux and Ubuntu installer packages
- Resources and support
- Contacting Dell EMC
If there is an operating system error due to a S.M.A.R.T error of the drive, then the event is not detected by the operating
system. If hard drives are part of a storage pool, then iSM does not monitor the drives for S.M.A.R.T failures.
On PowerEdge yx3x servers, S.M.A.R.T monitoring using software RAID is applicable only for the PDR22 event.
NOTE: S.M.A.R.T also requires iDRAC9 firmware 4.00.00.00 or later to be installed.
Operating system information
OpenManage Server Administrator currently shares operating system information and host name with iDRAC. The iDRAC
Service Module (iSM) provides similar information such as host operating system name, server host IP address information,
operating system version, and Fully Qualified Domain Name (FQDN) with iDRAC. The network interfaces on the host operating
system are also displayed. By default, the monitoring feature is enabled. This feature is available even if OpenManage Server
Administrator is installed on the host operating system.
You can also view host operating system network interface details, through the Redfish client plug-in for browsers.
NOTE: The minimum iDRAC firmware version required to view information using the Redfish client is 3.00.00.00.
NOTE: iSM is now supporting DHCP clients dhclient, dhcpd, wicked, netplan, and internal with Network Manager. If the
network configuration on the host operating system is configured using any other DHCP clients, then iSM will be unable
to monitor the network interface's change in states, for instance DHCP configuration of an interface. Hence, you may not
be able to view the change of the host operating system network interface details like DHCP status, DHCP server, default
gateway, DNS server in the iDRAC interfaces.
Lifecycle Controller log replication into operating
system
Lifecycle Controller log replication replicates the Lifecycle Controller (LC) log files to the operating system log files. All events
that have the operating system log option as the target in the Alerts page or in the equivalent RACADM or WS-Man interfaces
are replicated in the operating system log files. This process is similar to the system event log (SEL) replication performed by
OpenManage Server Administrator.
The default set of log files to be included in the operating system log files are the same as the logs configured for SNMP
traps or alerts. However, the events logged in the Lifecycle Controller log file after the iSM is installed are replicated to the
operating system log file. If OpenManage Server Administrator is installed, this monitoring feature is disabled to avoid duplicate
SEL entries in the operating system log file.
In iSM, you can customize the location to replicate the Lifecycle Controller log files. By default, the Lifecycle Controller log files
are replicated in the System group of the Windows logs folder in the Windows Event Viewer. You can replicate the Lifecycle
Controller logs to an existing group or create a folder in the Application and Services Logs folder in the Windows Event
Viewer. When iSM is already installed and if the host operating system undergoes a reboot or iSM is restarted, and iDRAC has
some Lifecycle Controller log files that are generated during this period of host downtime, then iSM log files these Lifecycle
Controller log files as past events in the operating system log file when the service starts.
NOTE:
You can choose the location to replicate the Lifecycle Controller log files only during iSM custom installation or iSM
modification.
NOTE: The source name of the iSM Lifecycle Controller log files has been changed from iDRAC Service Module to
Lifecycle Controller Log .
Automatic system recovery
The automatic system recovery feature is a hardware-based timer, which is used to reset the server in the event of a hardware
failure. You can perform automatic system recovery operations such as reboot, power cycle, or power off after a specified
time interval. This feature is enabled only when the operating system watchdog timer is disabled. If OpenManage Server
Administrator is installed, this monitoring feature is disabled to avoid duplicate watchdog timers.
You can configure three parameters in this feature from iDRAC interfaces:
30
iSM monitoring features