Release Notes

Known Issues and Resolutions
Issue 1
Description: If DSET 3.4 or later is running, and iDRAC Service Module is shut down or uninstalled; a Watchdog Timer Expiry
event is observed.
Issue 2
Description: After a successful first time configuration of iDRAC Access via Host OS using the iDRAC Service Module webpack;
the iDRAC interfaces may not be accessible due to default NetworkSecurity settings in iDRAC; irrespective of whether default
NetworkSecurity settings are enabled or disabled.
Reference: iDRAC GUI > Settings > Network > Advanced > Network Security. The IPRange Address and IPRange Mask
would be set to default values like 192.168.x.y and 255.255.255.0.
This can be resolved by reconfiguring iDRAC Access via Host OS using the PowerShell cmdlet. The IPRange can be set using
the cmdlet as shown in the example command below:
● For Windows,
○ Enable-iDRACAccessHostRoute -status true -port 12345 -IPRange 10.94.146.5/24.
● On Linux OSes,
○ Enable-iDRACAccessHostRoute 1 12345 10.94.146.5/24.
NOTE: The IP Range value should follow the CIDR format.
Issue 3
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, the following steps will resolve the issue.
1. Restart the iDRAC Service Module.
2. Restart the Microsoft Windows IP Helper service.
3. If Open Manage Server Administrator is running; restart the dsm_sa_datamgrservice.
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.
The issue has been addressed by Microsoft. For more information and the resolution to the issue, visit, https://
support.microsoft.com/en-us/kb/3156418
Issue 4
Description: On Microsoft Windows Nano operating system, when iDRAC Service Module 2.4.0 Appx is installed; a critical
App-Model-Runtime message is seen. However, there is no change in the functionality.
Issue 5
Description: On Linux Operating system, NVMe Safe removal operation from iDRAC interfaces (GUI/racadm/wsman) may fail on
systems having other pci devices along with NVMe. This issue is observed on blade chassis.
2