Release Notes

Issue 4: JIT-114656
Description: When iSM with TLS capability, for example: iSM 3.4.0 is installed on Linux operating systems, and the iSM client
certificate name is modified and iSM service is restarted, then communication between iSM and iDRAC ends.
Workaround: As a workaround, uninstall and then reinstall iSM 3.4.0.
Known issues on VMware ESXi operating systems
Issue 1
Description: After performing an iDRAC hard reset operation on certain VMware ESXi operating systems, the IPMI driver
ipmi_si_drv on ESXi 6.5 U2 and ipmi on ESXi 6.7 U1 operating systems may become unresponsive because of an existing issue in
the driver. If the IPMI driver becomes unresponsive, reload the IPMI driver.
The issue is observed on iDRAC Service Module v2.3 and later supported ESXi versions.
To reload the ipmi_si_drv:
● 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
● esxcli system wbem set -e 1
Alternatively, the administrator can also restart the host operating system to resolve the issue.
Issue 2: (JIT-118912)
Description: iSM uninstall or wbem stop causes an ungraceful stop of iSM CMPI modules which results in system V semaphore
leaks. Recurring system V semaphore leaks will impact iSM functionality. This is a known issue affecting vSphere ESXi 6.7. For
more information, see https://kb.vmware.com/s/article/66775.
5