Release Notes

Resolution/Workaround : Ensure that you clear the unused and stale entries
from Active Directory and then try a deployment.
32. Issue: ASM-6319 : On the Network Details page, released IP Addresses appear under
the old service.
Description : After you scale down a server or virtual machine, the IP address
used by the component is released and available for reuse in the future.
However, on the
Network Details page for the network the IP Address
belongs to, the IP Address is listed under the old service using it. This issue
occurs until the IP Address is used by another service.
Resolution/Workaround : None.
33. Issue: ASM-6498 :When adding network resources to a running service, for VMware
services that include VDS switches a port group must be entered.
Description : When adding network resources to a running service, for
VMware services that include VDS switches a port group must be entered.
The user interface will not allow you to proceed until a port group is selected
from the drop-down.
This port group will not be used, but must be selected.
Resolution/Workaround : Select a port group from the drop-down anytime
you are adding a network to a running VMware service which include VDS
switches.
34. Issue: ASM-6798 : Virtual machine or server deployments fail if Static Network Default
Gateway
is set to a network that does not have a gateway defined.
Description : The Static Network Default Gateway is used as the default
gateway on ASM-deployed servers or virtual machines. If the selected
network does not have a gateway defined, the server or virtual machine may
not be able to communicate with the ASM appliance and the service will fail.
Resolution/Workaround : Ensure that the network selected as the Static
Network Default Gateway
has a gateway defined.
35. Issue: ASM-6826 : After scaling down a virtual machine component, future deployments
with the same virtual machine name is not possible.
Description : After you scale down a virtual machine using the vRO plugin,
future deployments using the same virtual name that was used is not possible.
Resolution/Workaround : Restart the appliance.
36. Issue: ASM-6962 : During a retry of a previously failed deployment, the previous VM
deployment incorrectly indicates success if the OS install step in the configuration
process was successful.
Description : During a retry of a previously failed deployment, the previous VM
deployment incorrectly indicates success if the OS install step in the
configuration process was successful.
Resolution/Workaround : The VM that failed deployment will have to be
removed from the service and added as a new VM.
37. Issue:ASM-7170 : Configure VMware vSAN option for VSAN is enabled while creating
templates to deploy VMs to a cluster.
Description : When creating a template to deploy only VMs to a cluster, the
Configure VMware VSAN option is enabled by default. Selecting this option
causes the VM deployment to fail.
Workaround : While creating a template to deploy VMs to a cluster ensure