Release Notes
Table Of Contents
- Dell EMC iDRAC Service Module 3.2 Release Notes
- _
- Dell EMC iDRAC Service Module 3.2 Release Notes
- Importance
- What’s New
- User Notes for Supported Microsoft Windows Operating Systems
- Known Issues on Microsoft Windows Operating Systems
- Limitations on Microsoft Windows Operating Systems
- User Notes for Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server
- Known Issues on Linux Operating Systems
- Limitations on Linux Operating Systems
- Known Issues on VMware ESXi Operating Systems
- Limitations and Workarounds on VMware ESXi operating Systems
- Dell EMC iDRAC Service Module 3.2 Release Notes
Known Issues on Linux Operating Systems
Issue 1
Description: If DSET 3.4 or later is running, and iDRAC Service Module is shut down or uninstalled; a Watchdog Timer Expiry
event is observed.
Issue 2
Description: After performing an iDRAC Hard Reset operation on certain Linux operating systems, the IPMI driver (ipmi_si)
may become unresponsive because of an existing issue in the IPMI driver. If the IPMI driver becomes unresponsive, reload the
IPMI driver (ipmi_si).
The issue is seen on Linux kernel version prior to 3.15. An update is available in the following operating systems with Linux kernal
version 3.15 or later.
To reload the IPMI driver:
● modprobe -r ipmi_si — If the removal fails, then all applications (such as iDRAC Service Module and OpenManage
Server Administrator) using the ipmi_si need to be stopped and retry the operation.
● modprobe ipmi_si — Alternatively, the administrator can also restart the Host OS to resolve the issue.
Issue 3: JIT-88625
Description: When iDRAC Service Module 3.2.0 is installed on RHEL 6.9 Operating System with SELinux enabled in Enforcing
mode, AVC denial logs (AVC denial is noticed with iptables) are observed in /var/log/audit/audit.log while the following features
are enabled or disabled:
1. iDRAC Access via Host OS
2. Host SNMP Alerts
iDRAC Service Module 3.2.0 does not support explicit SELinux policies. No action is expected from the user. There is no
functionality impact to iSM features due to this. Future releases of iSM shall address the AVC denials.
Issue 4: JIT-93467
Description: iSM 3.2 OS DUP installation fails on SLES11SP4.
rpm-tool fails to handle OpenPGP subkeys and hence fails in integrity check.
Workaround: Upgrade rpm4.4.2.337.63.64.1.14842.3.PTF.1081280.x86_64.rpm. You can download this from https://
ptf.suse.com/a4508678dc8ee2c11453898fb347f199/sles11-sp4/14842/x86_64/20180222/.
Issue 5: JIT-96546
Description: To update to iSM 3.2 via idrac, Repair or Reinstall Service Module button is disabled if iSM 3.1 is already
running on the host OS and if the latest LC DUP is already in iDRAC.
Workaround: Stop iSM service on the host OS. Go to the iDRAC GUI and Repair or Reinstall Service Module button will be
enabled in the iDRAC GUI. Click on the tab and install ism.
Limitations on Linux Operating Systems
● BITS088419: Feature Lifecycle Log Replication on OS Log shows one-hour difference in the "EventTimeStamp" displayed in
OS log, when daylight saving is applied.
● JIT-87572: When iDRAC Hard Reset is disabled in iDRAC and user performs iDRACHardReset from the Hypervisor operating
systems like Citrix Xen, the result indicates success although iDRAC is not reset.
6