Release Notes

Issue 3
Description: A job for firmware rollback on PowerEdge MX7000 sleds, though allowed in the appliance, would fail. This happens due to the
fact that the firmware rollback is not supported on MX Series sleds discovered as part of MX7000 chassis discovery or in proxied state.
[136820]
Configuration management
Issue 1
Description: The Reclaim Identities and Profile Migration features are not supported for Emulex OneConnect Cards. [98511]
Issue 2
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 3
Description: The changed VLAN name and IDs are not updated on the target MX7000 chassis after a stateless deployment task is run.
[105156]
Issue 4
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 5
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 6
Description: The deployment task of an MX7000 chassis fails if proxy authentication in enabled in the configuration template with error:
'Unable to complete the request because the input value for Password is missing or an invalid value is entered'. [108779]
Issue 7
Description: The directory service details in an MX7000 chassis are overwritten after the device configuration template is deployed.
Issue 8
Description: After a chassis is removed from the MCM group, you must rediscover the lead and member chassis to create and deploy a
configuration template.
Issue 9
Description: The Migration Profile task fails if the user is not configured on the target device with the error: 'User Name is not configured
'. [107376]
Issue 10
Description: If the IP configuration of a discovered device is changed during template deployment (from DHCP to Static or vice versa),
the Boot to Network ISO operation fails. This happens as the appliance is unable to ping the target post template deployment.[113576]
Issue 11
Description: Unable to set Target iSCSI IQN on BIOS-iSCSI via reference server template deployment, as it fails with Invalid
AttributeValue error. The default iSCSI Target IQN format of the iSCSI controllers of devices such as PowerVault ME4012 array and
Equallogic PS array, is not accepted as a valid IQN format for deployment with IDRAC version 3.34.34.34. [132601]
Resolution: Select 'BIOS' attributes only for deployment.
Issue 12
Description: Creation of a chassis template from a reference M1000e chassis which has Firmware versions 6.10 or later fails if SMBv1 is
disabled in the appliance. [129049]
Resolution: Enable SMBv1 in the appliance using Application Settings > Console preferences > SMB settings to create chassis
templates from M1000e chassis with firmware versions 6.10 or later.
Issue 13
Description: Template Deployment with iDRAC Management IP option "Set static IP for each device" fails with error message "connection
lost" with IPV6 IP (Legacy(3.1)). It works with IPV4.
4
Dell EMC OpenManage Enterprise Version 3.2 Release Notes