Release Notes

Issue 2

Description: IPv6 support on Linux operating systems is not available for the following features:

• iSM Auto Update

• ismtech

• iDRAC GUI Launcher

• Inband iDRAC Access

Issue 3: JIT-102480

Description: When iDRAC Service Module 3.3.0 or later is installed on a system running the RHEL 6.10 operating system with SELinux

enabled in either permissive or enforcing modes, AVC denial logs, noted in iptables, are observed in /var/log/audit/audit.log

while the following features are enabled or disabled:

1. iDRAC access using the host operating system

2. Host SNMP alerts from the host

Workaround: iDRAC Service Module 3.3.0 and later does not support explicit SELinux policies. No action is expected from the user. iSM

functionality is not impacted. Future releases of iSM shall address the AVC denials.

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.