Release Notes
Table Of Contents
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 7
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 8
Description: The Reclaim Identities and Profile Migration features are not supported for Emulex OneConnect Cards. [98511]
Issue 9
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 10
Description: The changed VLAN name and IDs are not updated on the target MX7000 chassis after a stateless deployment
task is run. [105156]
Issue 11
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 12
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 13
Description: If a chassis template is deployed with a new static IP address on the FX2, VRTX, and M1000e chassis, then these
devices need to be re-discovered with the new IP for managing the device.
Issue 14
Description: The deployment task of an MX7000 chassis fails if proxy authentication is 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 15
Description: The directory service details in an MX7000 chassis are overwritten after the device configuration template is
deployed.
Issue 16
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 17
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 18
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 19
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 20
11