Release Notes

• DNS names must be in English.
Known Issues
The following section lists the known issues with ASM 7.6:
Issue [ASM-1152]: Unable to deploy a service using a template that contains more than one vCenter
cluster.
Description: If a template contains two clusters in the same vCenter instance, the service cannot be
deployed.
Resolution/Workaround: While deploying a service using a template, make sure the template contains
only a single vCenter Cluster.
Issue [ASM-1151]: CentOS is deployed successfully but ASM GUI displays a message that the
deployment is unsuccessful.
Description: Duplicate host names can cause this issue because the remote host operating system
checks the deployment with its host name. If an earlier host with a different service tag has checked in
with the same host name, the host name is not registered because the name already exists. If you
delete an earlier deployment, always use a unique host name.
Resolution/Workaround: Always use a unique host name.
Issue [ASM-1122]: vSwitch created on servers with 1 GB NICs do not tag ports correctly.
Description: 1 GB NICs is not supported.
Resolution/Workaround: None
Issue [ASM-1093]: While using Active Directory, ASM displays a message “An unexpected error has
occurred on the system. Please try again later”.
Description: This error occurs if invalid long values are used in the fields during Active Directory
instance creation.
Resolution/Workaround: None
Issue [ASM-1089]: The Phone number field does not allow special or alphabet characters.
Resolution/Workaround: While creating a user and entering the value for a phone number, use only
numeric characters.
Issue [ASM-1051]: You cannot select vNICs associated with vSwitches in VMware vCenter.
Description: During deployment of ESXi, vSwitches created by ASM do not allow you to select vNICs
because the vNICs are selected by ASM.
Resolution/Workaround: None
Issue [ASM-1013]: If you specify a Storage Pool that does not exist, a message indicating an error is
displayed
.