Users Guide
Table Of Contents
- iDRAC Service Module 3.0.1 User’s Guide
- Introduction
- Preinstallation setup
- Installing the iDRAC Service Module
- Initial installation of iDRAC Service Module via iDRAC for Windows
- Initial installation of iSM via iDRAC Express
- Initial installation of iDRAC Service Module via iDRAC for Linux
- Installing the iDRAC Service Module on Microsoft Windows operating systems
- Installing the iDRAC Service Module on Microsoft Windows operating systems
- Modifying the iDRAC Service Module components on Microsoft Windows operating systems
- Repairing the iDRAC Service Module on Microsoft Windows operating systems
- Uninstalling the iDRAC Service Module on Microsoft Windows operating systems
- Installing iDRAC Service Module on supported Linux operating system
- Installing the iDRAC Service Module on VMware ESXi
- Installing the iDRAC Service Module on Citrix XenServer
- 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
- In-band support for iDRAC SNMP alerts
- Enable WSMAN Remotely
- Auto-updating of iDRAC Service Module
- FullPowerCycle
- SupportAssist on the Box
- Frequently asked questions
- Linux installer packages
reset operation, such as racadm racresetcfg.
How do I troubleshoot the issue?
Ensure that the OS to iDRAC passthru channel is enabled. By default, it is disabled in factory mode. To enable the OS to IDRAC passthru
channel on iDRAC, use the following command, racadm set idrac.os-bmc.adminstate 1.
I am seeing the past Life Cycle Logs (LCL) alerts
targeted for SNMP traps replicated in Operating
System logs. Can I troubleshoot the issue?
iSM will not be able to distinguish between the past Life Cycle Log (LCL) alerts targeted for SNMP traps and past LCL alerts targeted for
OS Logs. Hence user may see past LCL alerts targeted for OS Logs in SNMP traps as well and vice versa.
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.
36
Frequently asked questions