Release Notes
Table Of Contents
● esxcli system wbem set –e 0
● esxcli system wbem set –e 1
JIT-87572
Description: When iDRAC hard reset is disabled in iDRAC and you perform iDRACHardReset from hypervisor operating
systems such as VMware ESXi, the result indicates success although iDRAC is not reset.
Known issues
Known issues on Microsoft Windows operating systems
You can configure the Windows Remote Management (WinRM) listener using a server authenticating certificate. If the
server authenticating certificate is not available, iDRAC Service Module will force-enable the WinRM listener using a
self-signed certificate. To configure the WinRM listener, create a self-signed certificate using the PowerShell cmdlet New-
SelfSignedCertificate from Microsoft Windows Server 2012 or later. In operating systems prior to Microsoft Windows
Server 2012 you cannot create a self-signed certificate due to the absence of PowerShell cmdlet.
Known issues on Linux operating systems
Issue 1
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_si.
The issue is seen on Linux kernel versions prior to 3.15. An update is available in the following operating systems with Linux
kernel version 3.15 or later.
To reload the IPMI driver:
● modprobe -r ipmi_si—If the removal fails, then stop any applications using the ipmi_si such as iDRAC Service Module
and OpenManage Server Administrator, and retry the operation.
● modprobe ipmi_si—Alternatively, the administrator can also restart the host operating system to resolve the issue.
Issue 2
Description: IPv6 support on Linux operating systems is not available for the following features:
● iSM Auto Update
● ismtech
● iDRAC GUI Launcher
● Inband iDRAC Access
Issue 3: JIT-102480
Description: When iDRAC Service Module 3.3.0 or later is installed on a system running the RHEL 6.10 operating system
with SELinux enabled in either permissive or enforcing modes, AVC denial logs, noted in iptables, are observed in /var/log/
audit/audit.log while the following features are enabled or disabled:
1. iDRAC access using the host operating system
2. Host SNMP alerts from the host
Workaround: iDRAC Service Module 3.3.0 and later does not support explicit SELinux policies. No action is expected from the
user. iSM functionality is not impacted. Future releases of iSM shall address the AVC denials.
4