Release Notes

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.
• Issue: ASM-6219: Backup and restore may reject valid CIFS share credentials.
Description: ASM may reject valid credentials in cases where CIFS shares have anonymous or guest privileges.
Resolution/Workaround: Clear the credentials, and retry the operation.
• Issue: ASM-6498: When adding network resources to a running service, for the VMware services that include vDS switches a port
group must be entered.
Description: When adding network resources to a running service, for the 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 includes vDS switches.
• 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 plug-in, future deployments using the same virtual name that was
used is not possible.
Resolution/Workaround: Restart the appliance.
• Issue: ASM-7255: Bare metal server deployment with the Intel Ethernet Converged network adapter x710 does not work due to a
driver issue.
Description: Bare metal server deployment on a server with the Intel Ethernet Converged network adapter x710 is not supported on
ASM 8.3.
Resolution/Workaround: Replace the network adapter with a supported model. For more information about the supported network
adapters, see the ASM Compatibility Matrix document available at Dell.com/asmdocs.
• Issue: ASM-7408: ESXi host intermittently loses connection to vCenter.
Description: ESXi host loses network connectivity with vCenter during ASM cluster component provisioning. This connectivity loss is
observed when the same physical NIC is used for both iSCSI and vSAN traffic.
Resolution/Workaround: Ensure that you use separate NICs for vSAN and iSCSI connection to the datastore.
• Issue: ASM-7501: Deployments fail if the ASM appliance does not have a default gateway.
Description: If the ASM appliance and ASM-deployed servers or VMs are on a different network, ASM uses the IP address of its
default gateway interface for communication between them. If the ASM appliance does not have a default gateway, the deployments
fail because ASM cannot find the IP address to use.
Resolution/Workaround: When configuring ASM appliance networking, ensure that a default gateway is specified. For DHCP
network configuration, ensure that the DHCP scope has a gateway set. For static network configuration, ensure that at least one
network interface is configured with a gateway.
• Issue: ASM-7553: Duplicate cluster names in a given vCenter instance cause issues.
Description: If two clusters have the same name in a given vCenter, even if they are in different data centers, ASM is unable to tear
down the cluster.
Resolution/Workaround: Manually remove the cluster from vCenter. Ensure that you do no select the cluster during a tear down of
an ASM server.
• Issue: ASM-7660: An error in the "executionpolicy" command causes the puppet agent to fail during the Windows post install.
Description: Running the puppet agent -t command after a windows post install failure during a puppet run, displays an error
message stating that the name of the cmdlet is not recognized and non-english characters are visible. This error occurs when you
copy and paste the script execution command from certain documents into the post install module in ASM for the Execute File
command.
Resolution/Workaround: Ensure that the text entered in the Execute File command is typed using a keyboard or copied only from
documents with no special or hidden characters.
• Issue: ASM-7852: Time zone and Network Time Protocol (NTP) set using the user interface is not applied.
Description: Setting the time zone and NTP using the ASM web interface does not update the time in the appliance.
Resolution/Workaround: Restart the appliance for the setting to take effect.
• Issue: ASM-8332: Incorrect time stamp attached to custom bundles.
Active System Manager Release 8.3.1 Release Notes
9