Release Notes

Limitations

Limitations on Microsoft Windows operating

systems

• Do not specify user profile folders (C:\Users\administrator\Desktop) as custom installation paths for installing iDRAC Service Module.

This is because services running on the system account cannot access such folders.

• You cannot view Lifecycle Controller logs in the new folder in the Event Viewer (169898) if you have recently changed the folder name

of the Lifecycle Controller logs in the Event Viewer. Microsoft recommends that you reboot the operating system to be able to view

the Lifecycle Controller logs under the new view name.

• When iDRAC Service Module is installed on Microsoft Windows operating systems using OS DUP, then the iSM Modify and Repair

operation from the Add/Remove programs throws and error:

Original source path of the file is now found

You can unzip the iSM DUP, double-click the MSI, and run repair.

Tracking number : 115250

• On Windows operating system, a feature that is enabled using the installer and disabled using any interface other than the installer, can

only be enabled using the same interface or the installer in GUI mode.

• Communication between iDRAC Service Module and iDRAC over IPv6 will work only on iDRAC firmware 2.70.70.70 or later.

Limitations on Linux operating system

• Feature Lifecycle Log Replication on OS log shows one-hour difference in the EventTimeStamp displayed in OS log when daylight

saving is applied.

Tracking number: BITS088419

• When iDRAC Hard Reset is disabled in iDRAC and you perform iDRACHardReset from the Hypervidor operating systems such as

Citrx Xen, the result indicates success although iDRAC is not reset.

Tracking number: 87572

• When iDRAC Service Module is communicating with iDRAC using IPv6 protocol, enabling the feature "InBand iDRAC Access" indicates

a successful message. But this feature is unavailable over IPv6 protocol. No action is required by the user.

Tracking number: 132983

• Communication between iDRAC Service Module and iDRAC over IPv6 will work only on iDRAC firmware 2.70.70.70 or later.

• On Red Hat Enterprise Linux 8.0 and Red Hat Enterprise Linux 8.1 Operating systems, unable to upload Support Assist Collection

report to backend.

Tracking number: JIT-148281

Limitations on VMware ESXi operating systems

• The iDRAC Access via Host OS feature is not supported on VMware ESXi Operating Systems.

• When Local Racadm set is disabled through iDRAC interfaces:

• iDRAC Service Module will fail to configure the OS to iDRAC Pass-through in the USB NIC mode.

• iDRAC Service Module functionality is restored when "Local racadm set" is enabled.

• EventID for Lifecycle Controller Logs replicated to OS log will be 0 for some of the past events.

• TrapID for In-band SNMP Traps will be 0 for some of the past traps.

• When iDRAC Hard Reset is disabled in iDRAC and user performs iDRACHardReset from the Hypervisor operating systems like

VMware ESXi, the result indicates success although iDRAC is not reset.

Limitations 11