Release Notes

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]
Configuration management
Issue 1
Description: If only VLANs are assigned to a target device during profile deployment, then these VLANs are not reclaimed by
the appliance when the profile is unassigned from the device. This behavior is not seen if other identities were assigned along
with VLAN definitions during the profile deployment. [174360]
Issue 2
Description: If only VLANs are assigned to a target device during profile deployment, then these VLANs are not reclaimed from
the device when the profile is migrated to a new device. This behavior is not seen if other identities were assigned along with
VLAN definitions during the profile deployment. [174576]
Issue 3
Description: Profile redeployment on FX2, VRTX, and M1000e chassis with edited VLAN configuration (tagged and untagged
values), clears only those VLAN values which were set during the initial deployment of the profile. The other VLAN values on the
ports that were not set during the initial deployment of the profile are not cleared during redeployment. [175692]
Issue 4
Description: Editing a Configuration template that is associated to a baseline which is either linked to a group of devices or a
large number of devices (20 or more) might cause a timeout with error message ' An application request timed out.
Please contact your support representative if the issue persists'. The changes however are saved to
the template in spite of the timeout. [164626]
Issue 5
Description: Same inventory details can be present on two servers post migration, as the 'true' target-specific attributes are
not reclaimed from the 'source' server as part of migration. [160622]
Issue 6
Description: The Reclaim Identities and Profile Migration features are not supported for Emulex OneConnect Cards. [98511]
Issue 7
Description: If the MX7000 chassis is in the 'monitored' state during stateless deployment, the deployment job fails because
the user does not have necessary privileges. Only the server configuration profile is imported. However, this information is not
displayed in the Task Execution section. [108484]
Issue 8
Description: The changed VLAN name and IDs are not updated on the target MX7000 chassis after a stateless deployment
task is run. [105156]
Issue 9
Description: If the IP setting is not configured on the discovered PowerEdge MX740C and PowerEdge MX840C, the Boot to
Network ISO operation is not run during the template deployment. [102887]
Issue 10
Description: After deploying an MX7000 chassis template, you cannot log in to the MX7000 chassis with LDAP credentials.
[107230]
Resolution: Manually update the LDAP Bind password to log in.
Issue 11
9