Manualshelf

Release Notes

ManualsBrandsDell ManualsActive System ManageriDRAC Service Module 4.x
12345678910
Known issues
● Issue 1:
Description:
When OpenManage Server Administrator (OMSA) is installed on the host operating system, the iDRAC Service Module
(iSM) communication with iDRAC will end after every 5 hours 30 minutes. No action is required by the user as the iSM
communication with iDRAC is automatically restored.
Workaround: There is no workaround available.
Tracking number: 173281
● Issue 2:
Description: When an incorrect SupportAssist proxy details are provided during the registration, a SIGKILL error message is
logged by kernel in the operating system event log, while stopping iDRAC Service Module (iSM). There might be a
semaphore leak because the iSM process is forcibly stopped by the kernel.
Workaround: There is no workaround available.
Tracking number: 161600
● Issue 2
Description:
When the customer has set the iDRAC DNS name with 27 characters or multiples of 27 characters, iSM communication with
iDRAC is not established and TLS Error is reported. The following message is logged in the operating system event log:
The iDRAC Service Module (iSM) is unable to communicate with iDRAC because the client or
server certificate is either unavailable or invalid
Workaround:
1. Reset iDRAC to factory defaults using the Reset iDRAC to Default Settings option.
2. Modify the iDRAC DNS name with a length of characters other than multiples of 27 characters.
3. Enable the USB NIC.
4. Manually start the iDRAC Service Module (iSM) service on the host operating system. To start the iSM service manually, do
the following with respect to the host operating system:
● On Microsoft Windows operating system, go to the Services menu, and start the iSM service as an Administrator.
● On Linux operating system, start dcism as a user by using the command systemctl start dcismeng.service
with the administrator or root privileges.
Tracking number: 165380
● Issue 4
Description:
When OSCollector Dup is updated on the iDRAC, the Job Queue page displays the job as "Firmware Update: Diagnostics"
instead of OSCollector.
Workaround: There is no workaround available.
Tracking number: 139485, 139088, 141091.
● Issue 5
Description:
When Federal Information Processing Standards (FIPS) mode is enabled on the host operating system, communication between
iDRAC Service Module and iDRAC is not established.
Workaround: There is no workaround available.
Tracking number: 158514, 158740, 158667, 159019.
4
Known issues 9