Release Notes
Table Of Contents
- Dell EMC iDRAC Service Module 3.6 Release Notes
- Release summary
- Compatibility
- New in this release
- Known issues
- Common issues
- A warning message indicating the iSM communication restart is observed in both iDRAC Lifecycle log files and operating system log files
- Job Queue page displays the job as Firmware Update instead of OSCollector
- Increased workload on the host interrupts the communication between iSM and iDRAC
- ISM0003 event message after replacing the system board
- Registering SupportAssist Enterprise
- Enabling operating system information
- Known issues on Microsoft Windows operating systems
- Invoke-iDRACHardReset and Invoke-FullPowerCycle are not functional
- Alert message is displayed when OMSA is installed and TSR is requested
- An internal error occurred when running the DCIM_View class
- A popup is displayed when uninstalling iSM
- Running WMI MOF query on DCIM results with no data
- iSM communication with iDRAC switches from IPv6 to IPv4
- During the repair or modify operation on Microsoft Windows 2016 operating system installation, communication between the iSM and iDRAC is not established
- Known issues on Linux operating systems
- iSM communication with iDRAC is dropped, when Enable-iDRACAccessHostRoute feature is enabled and firewall service is disabled
- ipmi_si IPMI_driver does not respond after iDRAC hard reset
- InBand iDRAC Access feature is unavailable in IPv6 protocol
- AVC denial with iptables
- A message is displayed when invoking iDRAC GUI Launcher for the first time
- Known issues on VMware ESXi operating systems
- Common issues
- Limitations
- User notes
- Resources and support
- Contacting Dell EMC
Known issues on VMware ESXi operating systems
iDRAC Service Module communication with iDRAC is interrupted in
ESXi 7.0 U1
Description: In VMware ESXi 7.0 U1, iDRAC Service Module (iSM) communication with iDRAC is dropped. No action is
required as the communication is restored automatically within 1 to 2 minutes.
Cause: Not available.
Workaround: Not available.
Tracking number: 172915
Communication is not restarting after performing Restart
Management Agents
Description: iDRAC Service Module is not restarting the communication with iDRAC after performing Restart
Management Agents on VMWare ESXi.
Cause: Not available.
Workaround: You must try performing Restart Management Agents again immediately after the first attempt.
Tracking number: 176426
IPMI driver becomes unresponsive on VMware ESXi
Description:
After performing an iDRAC hard reset operation on certain VMware ESXi, the ipmi_si_drv IPMI driver on
ESXi 6.5 U2 and ipmi IPMI drive on ESXi 6.7 U1 do not respond because of an existing issue in the IPMI
driver. If the IPMI driver becomes unresponsive, reload the ipmi_si_drv IPMI driver on ESXi 6.5 U2 and
ipmi IPMI drive on ESXi 6.7 U1.
Cause: Not available.
Workaround: The issue is observed in iDRAC Service Module 2.3 and later supported ESXi versions.
To reload the IPMI driver, run the following commands:
esxcli system wbem set -e 0
esxcfg-module -u ipmi_si_drv/ipmi => unload ipmi_si_drv/ipmi
esxcfg-module ipmi_si_drv/ipmi => load ipmi_si_drv/ipmi
esxcfg-module ipmi_si_drv/ipmi => load ipmi_si_drv/ipmi
esxcli system wbem set -e 1
If the removal fails, then applications such as iDRAC Service Module and OpenManage Server
Administrator must be stopped using the ipmi_si command, and then you can retry the operation.
Alternatively, the administrator can also restart the host operating system to resolve the issue.
Tracking number: Not available.
Performing iDRAC hard reset operation on VMware ESXi
Description:
To perform iDRAC hard reset operation on VMware ESXi operating system using the winrm command,
the iSM must be communicating with iDRAC.
Cause: Not available.
14 Known issues