Users Guide
Table Of Contents
- Dell EMC iDRAC Service Module 3.4 User’s Guide
- Contents
- Introduction
- Preinstallation setup
- Installing iDRAC Service Module
- Initial installation of iDRAC Service Module through iDRAC for Windows
- Initial installation of iSM through iDRAC Express
- Initial installation of iDRAC Service Module via iDRAC for Linux
- Installing iDRAC Service Module on Microsoft Windows operating systems
- Installing iDRAC Service Module on supported Linux operating systems
- Installing the iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module when the System Configuration Lock Down Mode is enabled
- Configuring the iDRAC Service Module
- iDRAC Service Module monitoring features
- Operating system information
- Lifecycle Controller log replication into operating system
- Automatic System Recovery
- Windows Management Instrumentation Providers
- Prepare to remove NVMe PCIe SSD device
- Remote iDRAC hard reset
- iDRAC access via Host OS
- Accessing iDRAC Via GUI, WS-man, Redfish, Remote RACADM
- In-band support for iDRAC SNMP alerts
- Enable WSMAN Remotely
- Auto-updating iDRAC Service Module
- FullPowerCycle
- SupportAssist on the Box
- Enabling the In-band SNMP Get feature—Linux
- Enabling the In-band SNMP Get feature—Windows
- iDRAC GUI Launcher
- Single sign-on (SSO) to iDRAC GUI from Host OS administrators desktop
- IPv6 communication between iSM and iDRAC over OS-BMC Passthru
- Enhanced security between iSM and iDRAC communication using TLS protocol
- Frequently asked questions
- Linux and Ubuntu installer packages
I am seeing 169.254.0.2 as the source IP address in the
iDRAC SNMP trap received via iSM. How do I troubleshoot
the issue?
On Linux OS, the iDRAC SNMP traps received via Host OS displays the hostname or source IP address as 169.254.0.2 instead of
the actual Host OS name or IP address. This is decided by the OS to populate the entry before rendering the trap to the user.
I have configured OS to iDRAC pass-through to LOM and
when I try to run dcism-sync, the update operation fails.
What can be done?
OS to iDRAC pass-through should be configured to USB-NIC mode. This is a pre-requisite for iDRAC Service Module installation
and update.
When Hyper-V is enabled in the Host OS, iSM is unable to
communicate with iDRAC. What should I do?
Enable the remote NDIS device under Network Adapter.
I am able to enable or disable the WMIInfo feature of
iSM on Linux and VMware ESXi Operating Systems using
racadm and WSMAN commands. Does this impact my iSM
configuration on the Host OS?
The WMIInfo feature of iSM is applicable only for Microsoft Windows Operating Systems. However, enabling or disabling this
feature from any of the iDRAC interfaces on any Operating System other than Microsoft Windows does not impact the iSM
configuration on the Host OS.
If I delete the IP address of the USBNIC interface on the
Host OS, then iSM is unable to communicate with iDRAC.
Starting iSM version 3.3, iSM configures the Host OS USBNIC interface only once. Subsequently, if you bring down the USBNIC
interface on the Host OS by deleting the IP address, making the interface link down or disabling the IPV4 or IPV6 address
on this interface, then iSM will retain the user configuration and does not override the interface settings. To restore the
communication between iSM and iDRAC, please restart the iSM service on the Host OS.
After installing iSM using the Batch file ISM_Win.BAT
from the iDRAC exposed logical partition "SMINST" on
46
Frequently asked questions