Release Notes

The issue is observed on all iDRAC Service Module v3.1 supported ESXi versions.
Steps to reload the ipmi_si_drv:
● /etc/init.d/sfcbd-watchdog stop
● esxcfg-module -u ipmi_si_drv => unload ipmi_si_drv
● esxcfg-module ipmi_si_drv => load ipmi_si_drv
● /etc/init.d/sfcbd-watchdog start — Alternatively, the administrator can also restart the Host OS to resolve the
issue.
Issue 5
When iDRAC Service Module is installed and running with the watchdog feature enabled on the host which has Redhat
Enterprise Linux 7.x OS versions, a graceful shutdown issued through iDRAC will result in the expiry of the BMC watchdog timer
with a "watchdog timer expired" event logged in the iDRAC Life Cycle Logs. When the BMC watchdog expires the configured
recovery action will be taken (e.g. power cycle).
The Graceful shutdown on iDRAC may happen in the following scenarios:
1. When the “Graceful Shutdown” on iDRAC GUI is manually executed by the user.
2. The DUP Firmware updates are done for any of the Hardware Components.
This event occurs due to a known issue documented for Redhat Enterprise Linux 7.x OS versions (http://topics-
cdn.dell.com/pdf/red-hat-entps-lx-v7.0_release%20notes_en-us.pdf).
No action is required by the user for this LCL event.
Workaround: Before performing either of the above mentioned scenarios, the ‘Watchdog Auto System Recovery’ action should
be set as “None”.
Installation
On the Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems, to perform an Express Install execute
dcism-setup.sh -x from the SYSMGMT/iSM/linux directory.
NOTE:
On Red Hat Enterprise Linux, SUSE Linux Enterprise Server, and VMware ESX Operating Systems, you will not have
the permission to run the script directly on the disk partition. Please use the format “sh ISM_LX.sh” to run the script and
initiate iDRAC Service Module installation.
For more information on installation instructions, including silent installation options, see the iDRAC Service Module Installation
Guide.
Limitation
● Do not specify user profile folders such as a desktop folder (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.
● Lifecycle Controller logs are not seen 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 (BITS113354).
● 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 (BITS180635).
● Feature Lifecycle Log Replication on OS Log shows one-hour difference in the EventTimeStamp displayed in OS log, when
daylight saving is applied. (BITS088419)
● The iDRAC Access via Host OS feature is not supported on VMware ESXi Operating Systems.
● When Local RACADM set is disabled through iDRAC interfaces,
○ The iDRAC Service Module will fail to configure the OS to iDRAC Pass-through in the USB NIC mode.
○ If OS to iDRAC Pass-through in the USB NIC mode is already configured, Watchdog feature does not work resulting in
ASR000 event.
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.
3