Release Notes
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.
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.
Issue: ASM-7003
: Existing template fields for VDS switches do not update after inventory
updates.
Description
: If you manually create a VMware Virtual Distributed Switch (VDS)
after creating a template in ASM, the new VDS switch is not displayed in the
available list of switches in the template.
Resolution/Workaround
: Remove the cluster component from the template,
create the VDS switches manually, and add the removed cluster component
to the template.
Issue: ASM-7255
: Baremetal server deployment with Intel Ethernet Converged network
adapter x710 does not work due to a driver issue.
Description
: Baremetal server deployment on a server with Intel 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 on 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 will use the IP address of its default gateway interface
for communication between them. If the ASM appliance does not have a
default gateway, the deployments will 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.