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
files, even when the operating system to iDRAC Pass-
thru over USBNIC is configured properly. Why do I get
this message?
iSM uses the operating system to iDRAC Pass-thru over USBNIC to establish communication with iDRAC. Sometimes, the
communication is not established though the USBNIC interface is configured with correct IP endpoints. This may happen when
the host operating system routing table has multiple entries for the same destination mask and the USBNIC destination is not
listed as the first one in routing order.
Table 17. Routing order details
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.94.148.1 0.0.0.0 UG 1024 0 0 em1
10.94.148.0 0.0.0.0 255.255.255.0 U 0 0 0 em1
link-local 0.0.0.0 255.255.255.0 U 0 0 0 em1
link-local 0.0.0.0 255.255.255.0 U 0 0 0 enp0s20u12u3
In the example enp0s20u12u3 is the USBNIC interface. The link-local destination mask is repeated, and the USBNIC is not the
first one listed. This results in the connectivity issue between iSM and iDRAC over the operating system to iDRAC Pass-through.
To troubleshoot the connectivity issue, ensure that the iDRAC USBNIC IPv4 address—by default it is 169.254.1.1—is reachable
from the host operating system. If it is not reachable from the host operating system do one of the following:
● Change the iDRAC USBNIC address on a unique destination mask.
● Delete the unwanted entries from the routing table to ensure that USBNIC is chosen by route when the host wants to reach
the iDRAC USBNIC IPv4 address.
Whenever I try to install iSM, the following error
message is displayed: This operating system is not
supported.
iSM can be installed only on supported operating systems. For information about operating systems that are supported, see
Supported operating systems.
I used the remote iDRAC hard reset feature to reset
the iDRAC. However, the IPMI is unresponsive and I
am not able to troubleshoot.
If you try to use the remote iDRAC hard reset feature on VMware ESXi operating system the IPMI drivers becomes
unresponsive, and because of this the iSM communication is stopped. You may have to reboot the server and load the IPMI
driver again to resolve the issue.
Where do I find the Replicated LifeCycle log on my
operating system?
To view the replicated Lifecycle log files:
Table 18. Operating system and it's location
Frequently asked questions 43