Release Notes
Table Of Contents
- Dell EMC iDRAC Service Module 3.2 Release Notes
- _
- Dell EMC iDRAC Service Module 3.2 Release Notes
- Importance
- What’s New
- User Notes for Supported Microsoft Windows Operating Systems
- Known Issues on Microsoft Windows Operating Systems
- Limitations on Microsoft Windows Operating Systems
- User Notes for Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server
- Known Issues on Linux Operating Systems
- Limitations on Linux Operating Systems
- Known Issues on VMware ESXi Operating Systems
- Limitations and Workarounds on VMware ESXi operating Systems
- Dell EMC iDRAC Service Module 3.2 Release Notes
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) may become unresponsive because of an existing issue in the IPMI driver. If the IPMI driver becomes
unresponsive, reload the IPMI driver (ipmi_si_drv).
The issue is observed on all iDRAC Service Module v2.3 supported ESXi versions.
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 2: JIT-102735
Description: On upgrading iSM 3.1 to iSM 3.2 from VUM, the ESXi OS is rebooting.
Issue 3: JIT-103063
Description: While updating iDRAC Service Module from v3.1 to v3.2 using VUM setup, the ESXi Host OS is going to maintain
mode automatically.
Issue 4: JIT-103060
Description: iSM cannot be installed through VUM after successful uninstallation.
Workaround for Issue 2, 3 and 4:
The upgrade of iDRAC Service Module Live VIB package for VMware ESXi from iSM 3.1 to iSM 3.2 using DellEMC VUM
repository requires a Host OS reboot. Alternatively, you can use the esxcli or PowerCLI interfaces to upgrade iDRAC Service
Module without a Host OS reboot.
Limitations and Workarounds 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.
○ 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.
● TrapID for In-band SNMP Traps will be 0 for some of the past traps.
● JIT-91716, JIT-90475: WSMan commands for remote iDRAC Hard Reset and remote Enabling or Diabling of
InBandSNMPTraps features are not functional on VMware ESXi 6.7.
Workaround: Stop and start WBEM in ESXi 6.7 using the following commands:
1. esxcli system wbem set –e 0
2. esxcli system wbem set –e 1
● JIT-82934: Due to mismatch between package name and VIB name, you may fail to deploy iDRAC Service Module
integrated with custom ESXi ISO image using PowerCLI.
Workaround: To integrate iDRAC Service Module VIB into custom ESXi ISO image:
7