Release Notes

8
characters.
Resolution/Workaround: Make sure while importing the Active Directory user name, the user name
contains only alphanumeric characters.
Issue [ASM-1001]: Unable to deploy a service for Fiber Channel storage component if the server
object is already mapped to the volume in Storage Center.
Description: If the server object is already mapped to a volume in Compellent Storage Center then a
service cannot be deployed for storage component.
Resolution/Workaround: Un-map the volume in Compellent Storage Center, and then retry the
service deployment.
Issue [ASM-1469]: Unable to deploy a Resource Module using CentOS 6.5 because devices do not
check in using ASM.
Description: ASM installs an agent in the deployed operating system using
a CIFs share, and this agent
should check in to confirm the deployment. If the minimal ISO is used on CentOS, the correct
packages for the samba-client to mount the share are not included. Therefore, the agent RPM cannot
be downloaded.
Resolution/Workaround: To install CentOS, do not use the minimal install because this does not
include the samba-client, the full ISOs are required.
Issue: [ASM-1576] Need to set vSwitch from beacon probing to "link status only" when using only two
NICs.
Description: When two physical NICs are used on a vSwitch, beacon probing should be disabled and
the setting should be set to "link status only". It is recommended to use beacon probing only when you
have three or more network adapters.
Resolution Workaround: In vCenter, for a host configuration, go to vSwitch properties and change
the settings for each vSwitch and port group to “Link status only”.
Issue: [ASM-1572] An incorrect license count is displayed for SCVMM.
Description: Currently, SCVMM is consumes users’ licenses.
Resolution/Workaround: None. Currently, ASM does not enforce license count. Therefore, resources
should still function normally even if a warning message is displayed on the ASM UI.
Issue: [ASM-1549] For EqualLogic storage, the volume size displayed in the Storage Group Details
page is slightly higher (2 7 GB) than the actual size.
Description: During discovery, volume sizes inventoried are displayed slightly higher than the actual
volumes in the EqualLogic. For example, a volume created as 110 GB is displayed as 112GB.
Resolution/Workaround: See the EqualLogic console for the correct volume size.