Release Notes

Description : The user interface is inaccessible when you login after updating
to ASM 8.2.
Resolution/Workaround : Ensure that you clear the browser cache after
updating ASM and before logging in the user interface.
26. Issue: ASM-5510 : Removing the battery from a controller on a Dell Compellent storage
device displays an inaccurate message.
Description : After you remove the controller battery on a Dell Compellent
storage device, an incorrect error message is displayed on the
Resource
page.
Resolution/Workaround : None.
27. Issue: ASM-5984 : Static IP addresses are requested or reserved for Server (Hardware
Only)
components.
Description : When deploying an ASM template with a Server (Hardware
Only)
configuration, IP addresses are reserved for all static networks included
on the network configuration of the component. Because this is a "hardware
only" component ASM does not configure the server to use these IPs.
Resolution/Workaround : Ensure that you do not assign static networks to
the
Server (Hardware Only) components or ensure that the static networks
that are used have enough IP addresses that can be assigned to the
component.
28. Issue: ASM-6170 : You can select unsupported ports for Virtual Link Trunking (VLT)
configuration on the I/O Aggregator.
Description : While configuring VLT on an I/O Aggregator, only ports 33 and
37 are supported. However, ASM allows you to select other non-supported
ports.
Resolution/Workaround : If you wish to configure VLT, ensure that you select
ports 33 and 37 in the ASM user interface.
29. Issue: ASM-6247 : After upgrading from 8.1.1 to 8.2, templates including virtual
distributed switches and port-group settings in a VMware Cluster component are not
imported.
Description : After an upgrade from ASM version 8.1.1 to 8.2, the virtual
distributed switches and port-group settings in an existing 8.1.1 templates
with a VMware Cluster component are not correctly populated.
Resolution/Workaround : While upgrading 8.1.1, if the VMware Virtual
Distributed setting is required, ensure that the cluster component is deleted
and recreated, and the appropriate data center is selected.
30. Issue: ASM-6299 : When building a template using the Import from Existing Template
option, you must renter the password, even though a password is displayed.
Description : When creating a server template using the Import from Existing
Template option, the password field is populated even though there is no
password set. If you proceed without updating the password and save it, the
server icon turns yellow. Attempting to publish the template displays an error
message stating that the admin password and confirmation password are
missing.
Resolution/Workaround : As a best practice for all imported templates, clear
the password field and set them correctly.
31. Issue: ASM-6311 : Stale Active Directory account entries for HyperV host and cluster can
fail HyperV deployments.
Description : A HyperV deployment may fail if stale Active Directory account
entries corresponding to a host or a cluster name are used in a deployment.