Release Notes

10
Issue: [ASM-1894] ASM cannot distinguish volumes with the same name in different Compellent
folders.
Description: If there are two existing volumes with the same name, but in different folders are
present in ASM inventory, ASM cannot distinguish these volumes.
Resolution/Workaround: Ensure unique names for volumes used by ASM in your Compellent
inventory.
Issue: [ASM-1897] ASM does not support any 1G integrated cards on the server.
Resolution/Workaround: Dell service or deployment team members need to manually disable the 1G
integrated cards on the server before using ASM to manage that server.
Issue: [ASM-2599] Unable to perform initial chassis discovery and configuration if firmware version
running on the I/O module is lower than the minimum firmware version.
Description: During initial chassis discovery and configuration using Discover Resources wizard, the
following error message is displayed if firmware version running on the I/O module, within the
chassis, is lower than the minimum firmware version recommended for ASM to manage.
“An unexpected error has occurred on the system. Please try again later.”
Resolution/Workaround: To resolve this issue, make sure to update the firmware version running on
the I/O module to the minimum supported version and retry the operation.
Issue: [ASM -1672] When cloning from reference server, if the target server for the configuration
already has FCoE offload set to enable on the network adapters for any ports or partitions, attempts
to configure iSCSI offload may fail.
Description: When cloning reference server configuration, where iSCSI offload is set to enabled, to a
target server, the attempts to set iSCSI offload on the target server may fail. This is because FCoE
offload is set to enable on the target server.
Resolution/Workaround: Ensure that FCoE offload is set to disabled on the target server before
attempting to enable iSCSI offload settings.
Issue: [ASM -2287] The server teardown operation does not remove the Active Directory and DNS
entries of the servers.
Description: If you tear down servers in a service, Active Directory and DNS entries of the server are
not removed if the associated cluster is not selected for tear down. In addition, in some cases, if ASM
is unable to communicate with the Active Directory or DNS server, these entries may also not be
removed.
Resolution/Workaround: To remove the Active Directory and DNS entries of the server, make sure to
select the associated cluster. If the issues persist, confirm that the Active Directory and DNS entries