Release Notes

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

Issue 11

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 12

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 13

Description: The Update Firmware button remains enabled even when there are no firmware catalogs available for upgrade or

downgrade. [108218]

Issue 14

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 15

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 16

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 17

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]

Configuration management

Issue 1: Improper alignment of compliance template attribute when the Upgrade notification bar is displayed.

Description: There is a misalignment of the compliance template attributes on the Template Details page when the Upgrade

notification bar is displayed. [203837]

Issue 2: Duplicate log messages are seen in the task execution history of Create and Deploy template jobs.

Description: Duplication of log messages in the task execution history is seen for Create Template and Deploy Template jobs

(Job Details page > View Details). [203788]

Issue 3: Template deployment fails if the reference server has a non-default port number.

Description: If a reference server has a non-default port number, then, the deployment of a template created using that

reference server fails on target servers that have default port numbers. The template deployment fails with a 'Connection with

server lost' error. [204048]

Issue 4 : VLAN attributes cannot be deployed using profiles unless deployed during template deployment.

Description: VLAN attribute changes fail on the target MX7000 sleds using profile redeployment, if the VLAN attributes were

not initially deployed on the MX7000 sleds during template deployment using the 'Propagate VLAN settings immediately' option.

[204044]

Resolution: Use the 'Propagate VLAN settings immediately' option every time VLAN changes are made during template

deployment.

Issue 5: Redeployment of an unassigned profile on a new target is unsuccessful.