Release Notes

classes, using an iDRAC Service Module on iDRAC firmware 4.00.00.00 or later, a MOF query will fail with an error message,
CLASS_NOT_FOUND. No action is required by the user.
Workaround: No workaround available for this issue.
Tracking number: 159276
● Description: While performing a repair or modify operation on a Microsoft Windows 2016 operating system installation,
occasionally the communication between the iDRAC Service Module and iDRAC is not established. Retry the operation.
Workaround: There is no workaround available.
Tracking number: 161320
Known issues on Linux operating systems
● Description: On Linux operating system, when IPv4 address of OS2iDRAC Passthrough interface is deleted on the host,
iDRAC Service Module logs the below message before restarting communication with iDRAC using IPv6:
The iDRAC Service Module is unable to communicate with iDRAC using the OS to iDRAC
Pass-through channel.
Workaround: There is no workaround available.
Tracking number: 173559
● 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 occurs in Linux kernel version prior to 3.15. An update is available in the following operating systems
with Linux kernal version 3.15 or later.
Steps 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.
IPv6 support on Linux operating systems are not available for the following features:
○ iSM Auto Update
○ ismtechInband iDRAC Access
● Description: When an iDRAC Service Module is communicating with iDRAC using IPv6 protocol, enabling the feature
InBand iDRAC Access indicates a successful message. But this feature is unavailable in IPv6 protocol.
Workaround: There is no workaround available.
● Description: When an 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 OS
○ 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. There is no functionality impact to iSM features due to this. Future releases of iSM shall address the AVC denials.
Tracking number: 102480
● Description: When TLS capable iSM (Example: iSM 3.4.0) is installed on Linux OSs' and the iSM client certificate name is
modified and iSM service is restarted, then iSM communication with iDRAC ends.
Workaround: As a workaround, user has to uninstall and install iSM 3.4.0
Tracking number: 114656
● Description: If the third octet of USBNIC IPv4 address is modified in iDRAC, then the iDRAC Service Module
communication with iDRAC will end.
Known issues
11