Release Notes

server, it is expected that whether the correct PXE server IP address will be
used in the dhcpd.conf that ASM creates.
o When multiple interfaces are used and DHCP is being served from the ASM
appliance, be sure that when doing the initial configuration on the appliance
“eth0” is selected as the interface that will reside on the PXE network as eth0
is what is used for DHCP .
• ASM-3493: Network scale up should only allow Public/Private networks.
o During the scale up of a network within a service allow only Public and
Private Networks, because the Public and Private networks are typically
selected for Workload networks .
• ASM 3490: Host and sub host groups cannot be used in separate deployments for Hyper-V
deployments.
o Hyper-V deployments uses one logical network and all hosts are assigned the
same logical network. In case of two deployments, if the first deployment
uses the parent host group and the second deployment uses a user defined
host group, then the second deployment with the user defined host group
fails.
• ASM-3150: Log event shows EqualLogic deployment fails.
o When you deploy EqualLogic storage, the Log event shows deployment is
failed. However, the ASM GUI shows deployment is successful.
o You should try an auto-retry.
• ASM-2381: In Mozilla Firefox, IQN/IPs are displayed as mandatory for Hyper-V template.
o If you open ASM in Mozilla Firefox and update Hyper-V template, ASM
prompts you to enter IQN/IPs, which are not valid.
o Use Google Chrome to update Hyper-V template
• ASM-3157: For SCVMM cluster provisioning, Active Directory must not contain any hosts
with the same name.
o When you provision a SCVMM cluster using a Hyper-V cluster creation
template, if the template has the AD entries for the Cluster that are persistent
and match the name you are trying to provision, the SCVMM cluster
deployment will fail.
o Active Directory and DNS conflicts must be resolved prior to a deployment if
you intend to use names that may already exist within your AD/DNS. ASM
requires the names to be removed from AD/DNS and these will be re-
provisioned during the template execution
• ASM-3129: Disk type information retrieved from ASM inventory is not the latest.
o After upgrading ASM from 8.0 to 8.1, to get the latest disk type information,
you need to run the inventory. If not, the disk type information will not be
available in 8.0 inventory. Or, you have to manually run inventory or wait till
ASM runs the inventory .
• ASM-2382: During volume scale up, duplicate volume lists existing volumes .
o During volume scale up, if you select the Duplicate option, the existing
volumes are displayed.
o If we select a volume that does not match the duplicated resource, then
there is no duplicating at all.
• ASM-2951: Error message is displayed during firmware update on C series.
o While performing firmware update on C series servers, the health status of
the C series switch changes to <gray> and the following error message is
displayed. Unknown error querying ipmi on host 172.31.32.142: Could not
retrieve IPMI status: ipmi_sensor_read: internal IPMI error.