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

IPv6 communication between iSM and iDRAC over
OS-BMC Passthru
The iSM supports both IPv4 and IPv6 modes of communication. After you install iSM, the iSM service attempts to connect to
iDRAC using IPv4 link-local address. If there is no IP address on the host USBNIC interface, iSM tries to configure IPv4 address
on the host side. This USBNIC interface configuration on the host operating system from iSM is done only once. iSM remains
disconnected from iDRAC if there is any subsequent scenario of incomplete configuration of USBNIC on the Host operating
system. If the connection fails even after configuring IPv4 address, iSM tries to connect to iDRAC using IPv6.
NOTE: This feature is supported only on Linux operating systems.
NOTE: If the IPv6 network stack is disabled on the host operating system, then iSM retries to communicate with iDRAC
using IPv4.
If either of the protocols are disabled, then iSM will not try to connect to iDRAC using the disabled protocol.
NOTE: If the iDRAC firmware version does not support IPv6 on USBNIC, the connection between iSM and iDRAC is
established using IPv4.
Respective audit messages are logged by iSM indicating the protocol version using which iSM connected with iDRAC.
NOTE: When iDRAC USBNIC is already configured with only IPv6 address on the host operating system and then iSM is
installed on the host, then iSM communication with iDRAC will start using IPv4 protocol.
Unsupported features with IPv6 protocol
The features that are not supported when iSM is configured with IPv6 protocol and IPv4 configuration is not available on the
USBNIC interface are:
● In-Band iDRAC Access
● In-Band SNMP Get
● idrac.local and drac.local
● Autoupdate of iSM
iSM monitoring features
43