Release Notes
Table Of Contents
- Dell EMC iDRAC Service Module 3.6 Release Notes
- Release summary
- Compatibility
- New in this release
- Known issues
- Common issues
- A warning message indicating the iSM communication restart is observed in both iDRAC Lifecycle log files and operating system log files
- Job Queue page displays the job as Firmware Update instead of OSCollector
- Increased workload on the host interrupts the communication between iSM and iDRAC
- ISM0003 event message after replacing the system board
- Registering SupportAssist Enterprise
- Enabling operating system information
- Known issues on Microsoft Windows operating systems
- Invoke-iDRACHardReset and Invoke-FullPowerCycle are not functional
- Alert message is displayed when OMSA is installed and TSR is requested
- An internal error occurred when running the DCIM_View class
- A popup is displayed when uninstalling iSM
- Running WMI MOF query on DCIM results with no data
- iSM communication with iDRAC switches from IPv6 to IPv4
- During the repair or modify operation on Microsoft Windows 2016 operating system installation, communication between the iSM and iDRAC is not established
- Known issues on Linux operating systems
- iSM communication with iDRAC is dropped, when Enable-iDRACAccessHostRoute feature is enabled and firewall service is disabled
- ipmi_si IPMI_driver does not respond after iDRAC hard reset
- InBand iDRAC Access feature is unavailable in IPv6 protocol
- AVC denial with iptables
- A message is displayed when invoking iDRAC GUI Launcher for the first time
- Known issues on VMware ESXi operating systems
- Common issues
- Limitations
- User notes
- Resources and support
- Contacting Dell EMC
iSM communication with iDRAC switches from IPv6 to IPv4
Description: When iDRAC Service Module (iSM) is communicating with iDRAC over IPv6 protocol on a Microsoft
Windows operating system, and if you perform an iDRAC Hard Reset operation or iDRAC firmware
upgrade or downgrade, then the communication switches back to IPv4.
Cause: Not available.
Workaround: There is no workaround and no action is required.
Tracking number: 138538, 146421
During the repair or modify operation on Microsoft Windows 2016
operating system installation, communication between the iSM and
iDRAC is not established
Description: While performing a repair or modify operation during Microsoft Windows 2016 operating system
installation, communication between the iSM and iDRAC might not established. Retry the operation.
Cause: Not available.
Workaround: There is no workaround available.
Tracking number: 161320
Known issues on Linux operating systems
iSM communication with iDRAC is dropped, when Enable-
iDRACAccessHostRoute feature is enabled and firewall service is
disabled
Description:
iSM communication with iDRAC is dropped, when Enable-iDRACAccessHostRoute feature is enabled and
firewall service is disabled in SUSE Linux Enterprise 12 SP2 operating system.
Cause: Not available.
Workaround: Not available.
Tracking number: 173354
ipmi_si IPMI_driver does not respond after iDRAC hard reset
Description:
After performing an iDRAC hard reset operation on certain Linux operating systems, the ipmi_si, IPMI
driver may not respond because of an existing issue in the IPMI driver. If the IPMI driver stops responding,
reload the ipmi_si IPMI driver.
Cause: Not available.
Workaround:
The issue occurs in Linux kernel version earlier to 3.15. An update is available in the following operating
systems with Linux kernel version 3.15 or later.
Steps to reload the IPMI driver:
● modprobe -r ipmi_si: If the removal fails, then applications such as iDRAC Service Module and
OpenManage Server Administrator must be stopped using the command: ipmi_si, and then you can
retry the operation.
12 Known issues