Dell EMC OpenManage Enterprise Version 3.4 Release Notes

Firmware and driver updates

Issue 1

Description: In-band driver updates are only supported on Windows with OpenSSH. Driver updates on third party SSH hosted on Windows, such as the CygwinSSH, are not supported. [157887]

Issue 2

Description: For the family of network adapter drivers, the operating system installed version, as seen in the Device Manager, differs from the version available in the online catalog. [157824]

Issue 3

Description: PERC H730P controller driver is not listed in the Firmware/Driver compliance report as it is currently not included in the online firmware/driver catalog. However, as this driver is a part of the Windows' server inventory, it is listed in the Inventory report of the windows devices.[163175]

Issue 4

Description: The firmware or driver compliance status of network switches, modular IOAs, and Dell storage devices may show as "Compliant" (but unselectable) in the firmware/driver compliance reports even though update of these devices are not supported by the Dell catalog.

Resolution: It is recommended to perform individual firmware or driver updates for these devices using their respective individual Update package. To perform individual firmware or driver updates, select a device on the All Devices page, and click View Details > Firmware/Drivers and select the individual package option. For more information about the list of unsupported devices, refer the OpenManage Enterprise version 3.4 User's Guide (Firmware/driver compliance baseline reports—'false' compliant devices)

Issue 5

Description: Driver update on PowerEdge RAID Controller (PERC) S140 controller fails when the SATA is in AHCI mode. [159735]

Resolution: As a prerequisite to update the PERC S140 controller driver, RAID mode must be enabled for SATA in BIOS. For more information, see the Dell EMC PowerEdge RAID Controller S140 User's Guide.

Issue 6

Description: The Clear Jobs and iDRAC reset functions for firmware updates are not supported for devices under the MCM chassis which are in a 'Proxied' onboarding state. [128765]

Issue 7

Description: AMD chipset driver update on the R6525 servers fails using OpenManage Enterprise Firmware/driver update feature. [159058]

Resolution: Windows (64-bit) driver updates for R6525 AMD chipsets must be done manually outside of the appliance.

Issue 8

Description: The firmware update task using the HTTP and HTTPS local shares fails, if these local shares were configured using proxy settings and are not listed in the proxy exception list. [151332]

Resolution: The HTTP and HTTPS local shares which are configured using the proxy settings, need to be listed in the proxy exception list before initiating any firmware update tasks using these shares.

Issue 9

Description: Firmware upgrade fails when iDRAC firmware versions older than 2.40.40.40 are upgraded directly to 2.63.60.61 with an error message Unable to verify Update Package signature. This failure happens as the firmware versions older than 2.40.40.40 cannot validate the latest SHA-256 digital signature of the Dell Update Packages. [146564]

Resolution: First upgrade the older iDRAC firmware versions to 2.40.40.40 before attempting an upgrade to iDRAC firmware version 2.63.60.61.

Issue 10

Description: The Update Firmware button remains enabled even when there are no firmware catalogs available for upgrade or downgrade. [108218]

Issue 11

Description: The firmware rollback on the PowerEdge MX7000 sleds is not supported. Also, rollback on sleds is not supported when the onboarding state of the sleds is Proxied.[116172]

Issue 12

Description: A job for firmware rollback on the PowerEdge MX7000 sleds, though allowed in the appliance, would fail. This happens because the firmware rollback is not supported on the MX series sleds discovered as part of MX7000 chassis discovery or in proxied state. [136820]

Issue 13

Description: When updating MX7000 chassis in the MCM mode, always make sure that the lead chassis is updated as the final step after updating all the member chassis. Also, chassis and sled firmware updates must be initiated separately. [168883]

Issue 14

Description: The Firmware Update task fails on the MCM member chassis with error message 'Syncing data with passive MM Task Failed. Completed With Errors'. [169333]