Release Notes

server into the BIOS -> Device Settings to view the updated MAC addresses.
Issue [ASM-1968]: Add server and Add storage should be disabled for failed deployments.
Description: If user clicks the Add Server or Add Storage on a failed deployment,
an Internal Error may
be displayed.
Resolution/Workaround: Do not click Add Server or Add Storage to scale up a failed deployment.
Issue [ASM-1894]: ASM cannot distinguish same named volumes in different Compellent folders.
Description: If two existing volumes having the same name, but they exist in different folders in
inventory, ASM cannot distinguish these volumes.
Resolution/Workaround: Make sure a unique name for volumes which is
used by ASM in your Compellent
inventory.
Issue [ASM-1871]: ASM vSwitch configuration requires single-purpose vSwitches.
Description: Currently ASM requires each vSwitch to have a unique purpose. This is for management,
migration, and iSCSI workload networks. For example, ASM cannot support having a single vSwitch that
has both management and migration port groups.
Resolution/Workaround: While configuring the NIC by using NIC partition, you must assign single
purpose network to each partition and assign same purpose network to multiple partitions. However,
you cannot assign multiple networks that have the different purpose to a single partition except PXE
network and the management network.
Issue [ASM 2014]: If there are one or many reserved disks accessible, WinPE image fails to identify the
disk on which the files has to be written as a result the process stops responding.
Description: While adding a new server to the existing service deployment, two volumes (cluster and
quorum) are configured for the existing servers. Access to the same volumes is added to the new server
before WinPE image deployment initiated. As a result, the WinPE execution for the new server stops
responding.
Resolution/Workaround:
Perform the following steps:
1. When the installation stops responding during the WinPE execution, connect to the Compellent
storage center and delete mappings of the cluster and quorum volumes.
2. Reboot the server.
3. Add the mapping back to the respective server-
object after the Windows installation is initiated.
Issue [ASM – 2002]: At the time of creating a template for Compellent storage component, there is no
option to select the RHEL from the Operating System Name drop-down menu.
Description: Compellent supports separate multi-pathing for RHEL 5.X and 6.X operating systems.
Currently these options are not available in Compellent storage object in the service template.