iDRAC9 Version 5.10.50.00 Release Notes

Release Summary

PDF

iDRAC firmware

Table 1. BIOS update failingUpdating BIOS using DUP method through iDRAC GUI, the update stops at 10% progression and finally fails with a timeout error.
Description	Updating BIOS using DUP method through iDRAC GUI, the update stops at 10% progression and finally fails with a timeout error.
Workaround	N/A
Systems Affected	All systems supported by this release.
Tracking number	225671

Table 2. System not powering on automatically after BIOS recovery After BIOS recovery is complete, Auto Power-on is not Initiating.
Description	After BIOS recovery is complete, Auto Power-on not Initiating.
Workaround	Power on the system manually to complete BIOS recovery process.
Systems Affected	All 15^th generation of PowerEdge servers with AMD.
Tracking number	232664/233395

Table 3. Information about Power Supply Unit (PSU) not displayed iDRAC GUI may not display the information about sensor, power, or voltage for PSUs.
Description	iDRAC GUI may not display the information about sensor, power, or voltage for PSUs.
Workaround	Remove and reinstall the PSU while iDRAC is running.
Systems Affected	PowerEdge XE8545 and PowerEdge R940XA.
Tracking number	231504/233949

Table 4. Unable to discard pending jobs During an iDRAC firmware rollback or update or iDRAC reboot, if a configuration job is in scheduled or is in running state, then deleting the pending values from iDRAC GUI using "Discard ALL Pending" option may fail.
Description	During an iDRAC firmware rollback or update or iDRAC reboot, if a configuration job is in scheduled or is in running state, then deleting the pending values from iDRAC GUI using "Discard ALL Pending" option may fail.
Workaround	Use the RACADM interface (racadm jobqueue delete -i JID_CLEARALL_FORCE).
Systems Affected	All systems supported by this release.
Tracking number	223742

Table 5. SubjectOrganizationalUnit not displayed in iDRAC GUI or Redfish SubjectOrganizationalUnit field is not available in GUI or Redfish interface for any security certificates that are stored in iDRAC certificate store.
Description	SubjectOrganizationalUnit field is not available in GUI or Redfish interface for any security certificates that are stored in iDRAC certificate store.
Workaround	Use the RACADM command to view the field: racadm sslcertview
Systems Affected	All systems supported by this release.
Tracking number	229355

Table 6. Sleds not powering on after a PSU firmware update After performing a PSU firmware update through DUP method, only one sled powers on automatically while others remain powered off.
Description	After performing a PSU firmware update through DUP method, only one sled powers on automatically while others remain powered off.
Workaround	Use iDRAC GUI to power on the remaining sleds.
Systems Affected	PowerEdge C6420
Tracking number	209713

Table 7. vFlash detaching after iDRAC firmware update Updating iDRAC firmware to version 4.40.00.00 or later may cause the vFlash partitions to detach on first boot after the update.
Description	Updating iDRAC firmware to version 4.40.00.00 or later may cause the vFlash partitions to detach on first boot after the update.
Workaround	Reattach the detached vFlash partitions through any iDRAC interfaces after the first boot.
Systems Affected	All systems supported by this release.
Tracking number	194849

Table 8. Backplane Rollback contents not populating in iDRACAfter updating backplane firmware to a newer version and then updating it back to a previous version from host OS, the backplane information is not displayed while trying to apply the firmware Rollback.
Description	After updating backplane firmware to a newer version and then updating it back to a previous version from host OS, the backplane information is not displayed while trying to apply the firmware Rollback.
Workaround	Perform the following: Reboot the iDRAC when an update is performed from host OS. Use any iDRAC interfaces (RACADM/GUI/Redfish) for backplane update operation.
Systems Affected	All systems supported by this release.
Tracking number	184368

Table 9. iDRAC time fails to synchronize when Server Configuration Profile is imported with SNTP settingsiDRAC time will not synchronize when Server Configuration Profile was exported with SNTP settings and then imported with SNTP settings.
Description	iDRAC time will not synchronize when Server Configuration Profile was exported with SNTP settings and then imported with SNTP settings.
Workaround	Configure NTP settings and export the Server configuration Profile. Import the Server configuration profile with NTP and manually configure SNTP settings.
Systems Affected	All systems supported by this release.
Tracking number	181069

Table 10. iDRAC unable to obtain the current time after rebootWhile the system is in power off state, iDRAC fails to obtain the current time after it is reset. Older logs are displayed until iDRAC synchronizes with current time.
Description	While the system is in power off state, iDRAC fails to obtain the current time after it is reset. Older logs are displayed until iDRAC synchronizes with current time.
Workaround	N/A
Systems Affected	All PowerEdge Rxxx5/Cxxx5 systems supported by this release.
Tracking number	183347

Table 11. iDRAC fails to communicate with CMC iDRAC may display stale or inaccurate information when there is a communication failure between iDRAC and CMC.
Description	iDRAC may display stale or inaccurate information when there is a communication failure between iDRAC and CMC.
Workaround	N/A
Systems Affected	PowerEdge FC640
Tracking number	226633