Release Notes

Known issues on Linux operating system
Table 5. Known issues on Linux operating system
Issue ID Functional area Description Workaround
Not available ipmi_si IPMI_driver
does not respond after
iDRAC hard reset.
After performing an iDRAC hard reset
operation on certain Linux operating
systems, the ipmi_si, IPMI driver may not
respond because of an existing issue in
the IPMI driver. If the IPMI driver stops
responding, reload the ipmi_si IPMI driver.
The issue occurs in Linux kernel
version earlier to 3.15. An update is
available in the following operating
systems with Linux kernel version
3.15 or later. Steps to reload the
IPMI driver:
● modprobe -r ipmi_si: If the
removal fails, then applications
such as iDRAC Service
Module and OpenManage Server
Administrator must be stopped
using the command: ipmi_si,
and then you can retry the
operation .
● modprobe ipmi_si
Alternatively, the administrator
can also restart the host
operating system to resolve the
issue
102480 AVC denial with
iptables
When iDRAC Service Module (iSM) is
installed on Red Hat Enterprise Linux
operating system with SELinux enabled
in the either of Permissive or Enforcing
modes, AVC denial with iptables in
the AVC denial log files are observed
in the /var/log/audit/audit.log
path, when the following features are
either enabled or disabled:
● iDRAC Access via Host operating
system
●
Host SNMP Alerts
iSM does not support explicit
SELinux policies. There is no
functionality impact to iSM features.
124514 A message is displayed
when invoking iDRAC
GUI Launcher for the
first time.
When invoking iDRAC GUI Launcher
for the first time either using
iDRACLauncher.sh or the program menu
shortcut, the following message is
displayed in operating system log files:
"localhost dbus-daemon[2369]:
[system] Activating via
systemd: service
name='net.reactivated.Fprint'u
nit='fprintd.service'
requested by ':1.18176' (uid=0
pid=126684 comm="sudo -l /opt/
dell/srvadmin/iSM/bin/
InvokeiDRACLau"label="unconfin
ed_u:unconfined_r:unconfined_t
:s0-s0:c0.c1023")"
There is no functional impact. No
action is required.
Known issues on VMware ESXi operating system
6