Release Notes

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
Issue 1
Description: On Microsoft Windows 2012 operating systems; if an iDRAC reset operation is performed when any of the iDRAC
sessions are opened using iDRAC access via Host OS feature, then the connection between iDRAC Service Module and iDRAC
may not be re-established. Also, the Microsoft Windows service IP Helper might stop running.
In such scenarios, do the following:
1. Restart the iDRAC Service Module.
2. Restart the Microsoft Windows IP Helper service.
3. If OpenManage Server Administrator is running, restart the dsm_sa_datamgr service.
Example:
● Open iDRAC GUI via the iDRAC access via Host OS feature.
● Perform an iDRAC firmware update from the GUI. This will reboot iDRAC with the new firmware.
● The iDRAC Service Module in the Host does not restart communication with iDRAC.
● IP Helper services stops running.
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-sign
certificate. To configure the Windows Remote Management (WinRM) listener, you can 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.
Issue 2: JIT-87075
While uninstalling iDRAC Service Module, a popup is displayed if the Firefox browser is opened. The popup prompts that Firefox
browser needs to be closed before continuing the uninstallation. Close the Firefox browser and click the Retry option to
continue the uninstallation.
Known Issues and Limitations 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
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.
4