Release Notes

Resolution/Workaround : Upgrade iDRAC firmware to 2.15 or later. For
servers which are on 2.10.10, validate Target Boot Device and RAID
Configuration are configured prior to deployment.
• Issue: ASM-4273 : Volumes deleted from a HyperV service in ASM are not removed
completely from the HyperV host.
o
Description : If you delete a storage volume from a HyperV service, the
volume will be deleted on the storage array and removed from ASM service,
but there may be stale references left on HyperV hosts.
Resolution/Workaround : Manually remove references to non-existent
volumes in HyperV using disk manager.
• Issue: ASM-4282: For HyperV services if only the last server is selected for teardown
without also including the cluster, the host will not be removed from the cluster.
o
Description : SCVMM prevents removing the last host from a cluster,
therefore if only the last host in a cluster is selected for teardown, ASM will
not be able to remove that host.
Resolution/Workaround : Whenever removing the last host from an SCVMM
cluster, also select the cluster for teardown.
• Issue: ASM-4294: In ASM 8.1.1, user cannot apply the license using Microsoft Internet
Explorer v.10
o Description : In ASM 8.1.1, When user applies the license using Internet
Explorer 10, the dialog box displaying the file name remains blank and the
license capacity is not displayed.
Resolution/Workaround : Use Google Chrome or Mozilla FireFox.
• Issue: ASM-4328 : After restore, operating system and firmware need to be able to be
rebuilt.
o
Description : After a restore, operating system and firmware repositories are
placeholders. The user must now remove the repositories and add new ones.
However, any existing templates or services that rely on the repositories will
prevent the existing repositories from being deleted in order to be re-added.
Hence, the user has to change the repositories for all templates, and any
existing services will have to be deleted in order to point to the correct
repository.
Resolution/Workaround : For any repositories, they cannot be used for new
templates or as an option for adding resources to a service, and provide a
method to rebuild the existing repository without requiring deletion.
• Issue: ASM-4399 : A message is displayed as “testing123" when the user upgrades from
version 8.1 to the latest version 8.1.1.
o
Description : When a user upgrades from ASM version 8.1 to version 8.1.1, a
pop-up message “testing123” is displayed. The message is displayed even
after the user restarts the VM guest appliance, refreshes the Web browser or
restarts the browser.
Resolution/Workaround : After the appliance update from 8.1 to 8.1.1, user
must clear the cache to address this issue.
• Issue: ASM-4448 : When a user logs into ASM and clicks on Template or Service page, a
blank page is displayed. sometimes the process of getting displayed occurs for a long time
and when the user performs a refresh, the user is logged out of the User Interface.
o
Description : Log into ASM 8.1.1 and navigate to the service or template page,
reload the application, a blank page is displayed.
o
Resolution/Workaround : To view the Service / Template page, clear the
cache and log into ASM.