The table lists the known issues in iDRAC Service Module 4.3.0.0 that are common on all supported operating systems.
Issue ID | Functional area | Description | Workaround |
---|---|---|---|
159410 | Increased workload on the host interrupts communication between iSM and iDRAC | When the workload on the host increases due to intensive task requests by the processor, communication between iSM and iDRAC is temporarily interrupted with the following warning message in the Lifecycle log file: The iDRAC Service Module communication with iDRAC has ended. | The connection automatically resumes and no action is required. |
161262 | ISM0003 event message after replacing the system board | If a USB NIC is enabled after the system board is replaced without restoring the configuration or after the iDRAC is reset to factory settings, you can observe the following ISM0003 event message on operating system log files before starting the communication: The iDRAC Service Module is unable to discover iDRAC from the operating system of the server. | No action is required |
216788 | RAC804 message logged after performing the iDRACHardReset operation | After performing the iDRACHardReset operation, the following RAC804 message is observed in the operating system logs: The System Configuration Lockdown mode is disabled. | No action is required and no feature is impacted. |
217506 | iDRAC UI is not accessible | The iDRAC UI is not accessible while switching to Federal Information Processing Standards (FIPS) mode on iDRAC. | Restart iDRAC |
225770 | iSM Limited Functionality mode | After performing the iDRAC reset operation while iSM is running in the Limited Functionality mode, the following issues are expected when iDRAC is active:
|
No functional impact on iSM running in the Limited mode. No action is required. |