Release Notes
Table Of Contents
Issue 5: IPMI driver may become responsive after iDRAC Hard Reset
operation on certain Linux operating systems
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).
Workaround: The issue is seen on Linux kernel version prior to 3.15. An update is available in the operating systems with Linux
kernel version 3.15 or later.
To reload the IPMI driver:
●
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.
Run modprobe -r ipmi_si to retry the operation.
● Alternatively, the administrator can also restart the Host operating system to resolve the issue .
Run modprobe ipmi_si to restart the Host operating system.
Issue 6: IPv6 support on Linux operating systems not available
Description: IPv6 support on Linux operating systems is not available for the following features:
● iSM Auto Update
● ismtech
● iDRAC GUI Launcher
● Inband iDRAC Access
Workaround: Not available.
Issue 7: AVC denial logs are seen when iDRAC Service Module 3.3.0 or
later is installed on RHEL 6.10 with SELinux enabled
Description: When iDRAC Service Module 3.3.0 or later is installed on RHEL 6.10 operating system with SELinux enabled
in either of Permissive or Enforcing modes, 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:
● iDRAC Access via Host operating system
● Host SNMP Alerts
Workaround: iDRAC Service Module 3.3.0 and later does not support explicit SELinux policies. No action is expected from the
user and there is no functionality impact to iSM features. Future releases of iSM shall address the AVC denials.
Tracking number: 102480
Issue 8: Communication between iSM and iDRAC disconnects when iSM
with TLS capability is installed
Description: When iSM with TLS capability (Example: iSM 3.4.0) is installed on Linux operating systems and the iSM client
certificate name is modified, the communication between iSM and iDRAC ends after the iSM service is restarted.
Workaround: User has to uninstall and reinstall iSM 3.4.0
Tracking number: 114656
10
Known Issues