Install Guide
Table Of Contents
- iDRAC Service Module 2.3 Installation Guide
- Introduction
- New in this release
- iDRAC Service Module monitoring features
- Operating system information
- Lifecycle Controller log replication into operating system
- Automatic system recovery feature
- Windows Management Instrumentation Providers
- Automatic Technical Support Report collection
- Prepare to remove NVMe PCIe SSD device
- Remote iDRAC hard reset
- iDRAC access via Host OS (Experimental Feature)
- In-band support for iDRAC SNMP alerts
- Supported features — operating systems matrix
- Co-existence of Server Administrator and iDRAC Service Module
- Software availability
- Downloading iDRAC Service Module
- Accessing documents from Dell support site
- Software license agreement
- Other documents you may need
- Preinstallation setup
- 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
- Configuring the iDRAC Service Module
- Frequently asked questions
- Do I need to uninstall Open Manage Server Administrator before installing or running the iDRAC Service Module?
- How do I know that the iDRAC Service Module is installed in my system?
- How do I know which version of the iDRAC Service Module I have in my system?
- What is the minimum permission level required to install the iDRAC Service Module?
- Whenever I try to install the iDRAC Service Module, it shows an error message This is not a supported server. Consult the User Guide for additional information about the supported servers. What should I do now?
- I see the messageThe iDRAC Service Module is unable to communicate with iDRAC using the OS to iDRAC Pass-through channel in the OS log, even when the OS to iDRAC Pass-through over USBNIC is configured properly. Why do I get this message?
- Whenever I try to install the iDRAC Service Module, an error message This operating system is not supported is displayed.
- I used the remote iDRAC hard reset feature to reset the iDRAC. However, the IPMI drives is unresponsive and I am not able to troubleshoot.
- Where do I find the Replicated LifeCycle log on my Operating System?
- What are the Linux dependent packages or executables I should install while completing the Linux installation?
- I created a custom folder in Windows Event Viewer, but the LC logs are not replicated in my custom folder. What do I have to do now to replicate the LC logs?
- I chose custom install option from the Graphical User Interface during iDRAC Service Module installation and disabled a feature, but I am not able to enable the feature using any of the other interfaces. How do I enable the feature again?
- Linux installer packages
Whenever I try to install the iDRAC Service Module, it
shows an error message This is not a supported server.
Consult the User Guide for additional information about
the supported servers. What should I do now?
Before installing the iDRAC Service Module, ensure that the server or the system on which the iDRAC
Service Module is to be installed is a Dell’s 12
th
generation PowerEdge server or later. Also make sure that
you have a 64-bit system.
I see the messageThe iDRAC Service Module is unable to
communicate with iDRAC using the OS to iDRAC Pass-
through channel in the OS log, even when the OS to
iDRAC Pass-through over USBNIC is configured properly.
Why do I get this message?
iDRAC Service Module uses the OS to iDRAC Pass-through 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 OS routing table has multiple
entries for the same destination mask and the USBNIC destination is not listed as the first one in routing
order.
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
enp0s20u12
u3
In the example enp0s20u12u3 is the USBNIC interface. The link-local destination mask is repeated and
the USBNIC is not the first one in order. This results in the connectivity issue between iDRAC Service
Module and iDRAC over the OS to iDRAC Pass-through. To troubleshoot the connectivity issue, you can
perform one of the following steps:
Ensure that the iDRAC USBNIC IPv4 address (by default it’s 169.254.0.1) is reachable from the host OS. If
not:
• Change the iDRAC USBNIC address on a unique destination mask.
• Delete the unwanted entries from the routing table to ensure USBNIC is chosen by route when the
host wants to reach the iDRAC USBNIC IPv4 address.
33