iDRAC9 Version 5.10.10.05 Release Notes

Release Summary

PDF

iDRAC firmware

Table 1. No notification for Virtual Media shutdownWhile accessing Virtual Media mapped with both ISO and IMG files on a Chrome browser with HTML5 Plugin, if the Virtual Media state is updated to Disabled then virtual media shuts down without any notification.
Description	While accessing Virtual Media mapped with both ISO and IMG files on a Chrome browser with HTML5 Plugin, if the Virtual Media state is updated to Disabled then virtual media shuts down without any notification.
Workaround	Launch the Virtual Media session on any other browser.
Systems Affected	All systems supported by this release.
Tracking number	204088

Table 2. Invalid Catalog file error In Lifecycle Controller, updating firmware through catalog update using NFS share fails with an error "Invalid catalog file".
Description	In Lifecycle Controller (LC), updating firmware through catalog update using NFS share fails with an error "Invalid catalog file".
Workaround	Ensure that you add the catalog file name and extension in the Source NFS path, or update using any other network shares.
Systems Affected	All systems supported by this release.
Tracking number	204784

Table 3. Firmware update using FTP fails Firmware update fails from FTP share when an HTTP non-auth (without credentials) proxy is used.
Description	Firmware update fails from FTP share when an HTTP non-auth (without credentials) proxy is used.
Workaround	Use any proxy with credentials.
Systems Affected	All systems supported by this release.
Tracking number	211950

Table 4. Probe name for GPU displayed incorrectly In iDRAC GUI Cooling page, Temperature probe name of GPU displays "System Board SLOTx Temp" instead of "System Board GPUx Temp".
Description	In iDRAC GUI Cooling page, Temperature probe name of GPU displays "System Board SLOTx Temp" instead of "System Board GPUx Temp".
Workaround	N/A
Systems Affected	All systems supported by this release.
Tracking number	214506

Table 5. 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 6. ManagedSystemSize displaying incorrect value The property ManagedSystemSize may display an incorrect value in the iDRAC system inventory page.
Description	The property ManagedSystemSize may display an incorrect value in the iDRAC system inventory page.
Workaround	N/A
Systems Affected	All systems supported by this release.
Tracking number	212710

Table 7. Voltage or Current information for PSU not availableAfter an iDRAC firmware update, iDRAC GUI or remote RACADM may fail to display information about the second PSU.
Description	After an iDRAC firmware update, iDRAC GUI or remote RACADM may fail to display information about the second PSU.
Workaround	Perform an iDRAC reset.
Systems Affected	All systems supported by this release.
Tracking number	207006

Table 8. 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 9. 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 10. 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 11. 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