Release Notes

JIT-117904
Description: In GNOME-enabled Linux variants, if the auto-suspend feature is enabled, the operating system gets into suspended state
after a certain idle time. This logs a message, Watchdog Timer Expired, in the Lifecycle Log, if the operating system is not awake before
the watchdog expiry time is reached.
JIT-117517
Description: iSM start communications with iDRAC using IPv4 stack by default. If you bring down the OS-BMC Passthrough, host side
interface using ifconfig <interface-name> down, the communication will switch to IPv6 once the interface is brought up.
Limitations and workarounds on VMware ESXi operating systems
iDRAC access through the host operating system feature is not supported on VMware ESXi operating systems.
When local racadm set is disabled through iDRAC interfaces:
• iDRAC Service Module fails to configure the OS-to-iDRAC Passthrough in USB NIC mode.
• iDRAC Service Module functionality is restored when local racadm set is enabled.
EventID for Lifecycle Controller logs replicated into the operating system log is 0 for some past events.
TrapID for in-band SNMP traps is 0 for some past traps.
JIT-91716 and JIT-90475
Description: WSMan commands for remote iDRAC hard reset and remote enabling or disabling of InBandSNMPTraps features are not
functional on VMware ESXi 6.7 or later.
Workaround: Stop and start WBEM in ESXi 6.7 and later using the following commands:
• 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.
5