- Release Summary
Description | The following Telemetry reports may intermittently miss a few metrics: PowerMetrics, PSUMetrics, ThermalMetrics, StorageSensor, MemeorySensor, AggregationMetrics, SystemUsage, FPGASensor, PowerStataistics, PowerStatistics, CPUMemMetrics. |
Workaround | Perform any of the following:
|
Systems Affected | All systems supported by this release. |
Tracking number | 259718 |
Description | While performing an iDRAC stress test, SEL logs may display critical system messages and iDRAC also displays the System Health status as critical. |
Workaround | Perform an iDRAC reboot. |
Systems Affected | PowerEdge XE2420 |
Tracking number | 239644 |
Description | Maximum temperature for DIMMs may be displayed as N/A intermittently in all iDRAC interfaces. |
Workaround | Perform an iDRAC reset. |
Systems Affected | PowerEdge R250 |
Tracking number | 239031 |
Description | iDRAC displays the system status as Critical while a PSU firmware update is in progress. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 237581 |
Description | If LCAggregation feature is enabled in iDRAC and iDRAC receives repeated login, logout in few seconds of interval along with other events, some events may not be displayed in LC logs in iDRAC GUI. |
Workaround | Check the log entries in the TSR, or the exported xml, or in the RACADM LC logs. |
Systems Affected | All systems supported by this release. |
Tracking number | 231290/231074 |
Description | Lifecycle (LC) logs may display "CPU temperature is greater than the upper critical threshold" during a system-warm reboot. |
Workaround | A deassertion event is logged automatically after a few seconds that display that the temperature is within range. |
Systems Affected | PowerEdge R7525 and PowerEdge R6525 |
Tracking number | 228837 |
Description | SEL may continuously report PSU-related errors even after the error is fixed. |
Workaround | N/A |
Systems Affected | All 15th generation PowerEdge systems supported by this release. |
Tracking number | 228719 |
Description | Importing SCP file that was exported from a system with iDRAC version 5.00.15.00 to a system with iDRAC version 5.00.20.00 or later versions may fail. |
Workaround | Update the iDRAC version of the system exporting SCP file to iDRAC version 5.00.20.00 and then try exporting the file again. |
Systems Affected | All systems supported by this release. |
Tracking number | 213900 |
Description | New SEL events were introduced in iDRAC versions 4.4x. If iDRAC is rolled back to an earlier version, then new events logged in the version of iDRAC before it was rolled back may be displayed as an unknown event. |
Workaround | N/A |
Systems Affected | All PowerEdge Rx5x5 or Cx5x5 series servers supported by this release. |
Tracking number | 186384 |
Description | PR1 & PR10 logs are displayed in Lifecycle logs for PSUs when Retire and Repurpose operation is executed. This doesn't impact server functionality. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 186119 |
Description | After performing a server warm reboot, iDRAC may report Disk Inserted in LC logs for drives behind HBA. Please ignore the log entry. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 144819 and 141414 |
Description | When the system is powered on manually after performing a system erase on LC data, several messages are displayed in LC logs for PSU stating “PR7 New device detected: POWER SUPPLY (PSU.Slot.X)”. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 129440 |