Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

iDRAC9 Version 7.00.00.00 Release Notes

PDF

Monitoring and alerting

Table 1. RAC0787 error on Firmware and Hardware Inventory page The firmware and Hardware Inventory page in the iDRAC GUI displays an error RAC0787.
Description The firmware and Hardware Inventory page in the iDRAC GUI displays an error RAC0787.
Workaround Perform an iDRAC reboot.
Systems Affected All systems supported by this release.
Tracking number 273862
Table 2. Delay in crash capture logs If the server experiences a CPU error such as RSOD, iDRAC may take longer to collect logs about the crash.
Description If the server experiences a CPU error such as RSOD, iDRAC may take longer to collect logs about the crash.
Workaround N/A (Power cycle the system if it takes more than ten minutes to restart).
Systems Affected All 15th and 16th generation of PowerEdge systems with Intel CPU.
Tracking number 262320
Table 3. PR logs about PSU If the system fails power on due to a loose cable connection, informational PR logs (PR7, PR1, PR10) for PSU are generated in Lifecycle logs.
Description If the system fails power on due to a loose cable connection, informational PR logs (PR7, PR1, PR10) for PSU are generated in Lifecycle logs.
Workaround There is no functional impact. Reconnect the cable or ignore the log if the system is already powered on.
Systems Affected All systems supported by this release.
Tracking number 259806
Table 4. SEL events may not be correctly displayed in the earlier versions of iDRACNew 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.
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
Table 5. PR1 & PR10 Lifecycle logs displayed during Retire and Repurpose operation PR1 & PR10 logs are displayed in Lifecycle logs for PSUs when Retire and Repurpose operation is executed. This doesn't impact server functionality.
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
Table 6. After a warm reboot, LC logs display Disk Inserted After performing a server warm reboot, iDRAC may report Disk Inserted in LC logs for drives behind HBA. Please ignore the log entry.
Description After performing a server warm reboot, iDRAC may report Disk Inserted in LC logs for drives behind HBA.
Workaround Ignore the log entry.
Systems Affected All systems supported by this release.
Tracking number 144819 and 141414
Table 7. Repetitive PR7 messages related to PSU in LC logs after a system erase operation 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)”.
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

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\