Release Notes

6
Known Issues
The following section lists the known issues with ASM 8.0:
Issue [ASM-1122]: vSwitch created on servers with 1GB NICs do not tag ports correctly.
Description: 1GB NICs are 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-1013]: If you specify a Storage Pool that does not exist, a message indicating an error is
displayed.
Description: After creating a storage template, if you type a Storage Pool name that does not exist
then the deployment indicates an error.
Resolution/Workaround: None
Issue [ASM-953]: SD Card Mirroring must be enabled on all the physical servers.
Description: The deployment to bare metal server do not consider dual SD card. Thus ASM could
deploy the operating system in one SD card and boot from the other. Servers are shipped from the
factory with appropriate settings.
Resolution/Workaround: If this issue occurs, make sure that SD card mirroring is enabled on the
server.
Issue [ASM-836]: If you delete a user in Active Directory, the user still exists in ASM Users list.
Description: If an Active Directory user is already imported to ASM and the user is deleted in Active
Directory server, you can no longer log in again. The user exists in the ASM Users list and can still edit
the details about the user. If you add the deleted user in Active Directory again, you must log in using
a new password.
Resolution/Workaround: None
Issue [ASM-837]: The group a user belongs to in Active Directory is not associated with the role that
the user must be associated in ASM.
Description: A user under a group in Active Directory is not associated with the role that the user