Users Guide
Table Of Contents
- Dell EMC iDRAC Service Module 3.6 User’s Guide
- 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 (SSO) 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
I am seeing 169.254.0.2 as the source IP address in
the iDRAC SNMP trap received through iSM. How do I
troubleshoot the issue?
On the Linux operating system, the iDRAC SNMP traps received through the host operating system displays the hostname or
source IP address as 169.254.0.2 instead of the actual host operating system name or IP address. This is determined by the
operating system to populate the entry before rendering the trap to the user.
I have configured my operating system to iDRAC
pass-thru to LOM and when I try to run dcism-sync,
the update operation fails. What can be done?
Operating system to iDRAC pass-thru must be configured to use USB-NIC mode. This is a pre-requisite for iSM installation and
update.
I can enable or disable the WMIInfo feature of iSM on
Linux and VMware ESXi using RACADM and WS-Man
commands. Does this impact my iSM configuration on
the host operating system?
The WMIInfo feature of iSM is applicable only to 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 operating system.
If I delete the IP address of the USBNIC interface
on the host operating system, then iSM is unable to
communicate with iDRAC.
The iSM configures the host operating system USBNIC interface only once. Later, if you bring down the USBNIC interface on
the host operating system 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, restart the iSM service on the host operating system.
After installing iSM using the batch file ISM_Win.BAT
from the iDRAC exposed logical partition "SMINST"
on Microsoft Windows operating system, I see a
Frequently asked questions
49