Release Notes

Description: After creating custom bundles, an incorrect time stamp is displayed for the bundles on the View Bundles page.
Resolution/Workaround: Set NTP and restart the appliance to fix the issue.
• Issue: ASM-8344: PXE boot on a second Intel NIC fails.
Description: If you are using a server with two Intel X710 NICs, operating system installation network assigned to the second port fails
with the message that the NIC cannot be found.
Resolution/Workaround: Ensure that you assign the operating system installation network to the first port of the first NIC.
• Issue: ASM-8399: Not all storage settings are supported when deploying templates using the VMware vRealize Orchestrator (vRO)
plug-in.
Description: Attempting to run the vRO workflows to scale up storage volumes with autogenerated volume names do not succeed
and result in a service failure.
Resolution/Workaround: Ensure that you select only the Specify a new storage volume name now option in the templates that
you want to deploy using vRO.
• Issue: ASM-8386: Using inconsistent network combinations on an ESXi server network configuration may result in VMware cluster
configuration failure. In this case, the following cluster log message is displayed: The resource 'vmnic4' is in use.
Description: The server network configuration is used to determine NIC teaming on the ESXi host. Different NIC ports or partitions
that are part of a team must have the same networks on them since the team forms one virtual NIC. In some cases, a network
configuration that violates this rule may get created and that would result in a failure when trying to create the NIC teams.
Resolution/Workaround: Edit the server network configuration to ensure that the same combinations of networks are used on the
various NIC ports and/or partitions.
An example of a valid network configuration is:
Port 1: Hypervisor Management, Hypervisor Migration Port 2: Hyeprvisor Management, Hypervisor Migration
An example of an invalid network configuraiton is:
Port 1: Hypervisor Management, Hypervisor Migration Port 2: Hyeprvisor Management
In the latter case ports 1 and 2 must belong to the same NIC team and therefore must have the same combination of networks on
them.
• Issue: ASM-8499: ASM reports an error while processing storage components.
Description: When creating a volume on a newly configured Compellent storage with no existing volume, ASM fails to create a
volume and the following error message is displayed: Error: No Storage Type found on Storage Center, you must
create one prior to trying to create a volume.
Resolution/Workaround: Ensure that you create a temporary volume before initiating an ASM service to create a volume on a newly
configured Compellent storage. This instantiates a storage type on the Dell Compellent storage device and which ASM uses for the
volume creation process.
• Issue: ASM-8524: Restore operations take longer to complete if NTP is not configured.
Description: When restoring an appliance, if NTP is not set and the time is incorrect, the restore may block you from logging in after
the 1-hour timeout.
Resolution/Workaround: Before performing a restore, verify that NTP settings have been applied to ASM.
• Issue: ASM-8586: Datastore entry is not removed from vCenter when scaling down the datastore set as the syslog location.
Description: After removing a volume from a shared storage, the datastore entry that is set as the syslog location is not removed.
Resolution/Workaround: Retry the service to reconfigure the syslog location and then manually remove the datastore.
• Issue: ASM-8611: Deploying a cluster with multiple networks using the same vDS or port group name causes the deployment to fail.
Description: If you specify the same name for multiple virtual distributed switches (vDS) or distributed port groups, there is a
possibility that the settings may get applied to the wrong vDS or port group causing the deployment to fail.
Resolution/Workaround: Ensure that the vDS and port groups have unique names.
• Issue: ASM-8721: Cannot complete Boot from SAN deployment due to the following error: An invalid host name is typed.
Description: When attempting to deploy a template with only server and storage for boot from SAN, the deployment does not start
and reports the following error: An invalid host name is typed.
Resolution/Workaround: Perform the following steps:
1. On the ASM user interface, click Templates.
2. Select the template to edit, click Edit.
10
Active System Manager Release 8.3.1 Release Notes