Users Guide
Table Of Contents
- Dell EMC iDRAC Service Module 4.0.1 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
- 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 Passthru
- Frequently asked questions
- Linux and Ubuntu installer packages
- Resources and support
- Contacting Dell EMC
NOTE: In Windows, when the DLL authentication failure event (SEC0704) is triggered, the Auto System Recovery Action
set in the iSM settings page will be performed. iSM must be repaired or reinstalled to restore to the default state.
Windows Management Instrumentation Providers
Windows Management Instrumentation Providers available with iSM exposes hardware data through Windows Management
Instrumentation (WMI). WMI is a set of extensions to the Windows Driver Model that provide 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 help to integrate with
Systems Management Consoles such as Microsoft System Center and enable scripting to manage Microsoft Windows servers.
The namespace that is used is \\root\cimv2\dcim. The supported queries are Enumeration and Get. You can use any of
the WMI client interfaces such as winrm, Powershell, WMIC, WBEMTEST to query the iDRAC supported profiles through the
host operating system.
NOTE: When multiple WMI classes are simultaneously enumerated, the iSM might restart communication with the iDRAC.
No action that is required.
Prepare to remove a NVMe PCIe SSD device
You can remove a Non-Volatile Memory Express (NVMe) Peripheral Component Interconnect Express (PCIe) Solid state device
(SSD) without shutting down or rebooting the system. When you are removing a device, all the activities that are associated
with the device must be stopped to prevent data loss. Stop any activities manually before performing the Prepare to remove
task. To prevent the loss of data use the Prepare to Remove option, after which you can remove the NVMe PCIe SSD
physically. The Prepare to remove operation does the validation, and checks if the device is busy with any activity or not. If the
device is busy with an activity, the Prepare to remove operation will not proceed.
NOTE: Follow the VMware documented prerequisites before performing Prepare to Remove operation in VMware ESXi.
Remote iDRAC hard reset
iDRAC may become unresponsive for various reasons. iSM can fully reset an unresponsive iDRAC8 or iDRAC9 controller by
temporarily removing power to the iDRAC controller without affecting operating system production. This feature can only be
disabled from the iSM page in iDRAC using the iDRAC interfaces.
To reset iDRAC, use the following Windows PowerShell or Linux shell command:
./Invoke-iDRACHardReset
iDRAC access via Host OS
Using PowerEdge Servers, you can manage the hardware or the firmware of a device through iDRAC by configuring an iDRAC
dedicated network. Through the dedicated network port, you can access the iDRAC interfaces such as UI, WS-Man, RACADM,
and the Redfish client.
The prerequisite to manage the hardware or the firmware is to have a dedicated connection between a device and the
supported iDRAC interface. Using iDRAC access via Host OS, you can connect to an iDRAC interface from an operating system
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 network.
You can select any of the following subfeatures to enable the iDRAC access via Host OS:
● Access via GUI, WS-Man, Redfish, Remote RACADM
● In-Band SNMP Traps
● Access via SNMP Get
If you select iDRAC access via Host OS, all the subfeatures are selected by default. If you want to select any one of the
individual subfeatures, you can select a particular feature and enable it.
28
iSM monitoring features