Release Notes

Issue: [ASM-1564] A cluster cannot be deployed when multiple storage volumes are added to a cluster.
Description:
When creating a template that has two servers and each had a single EQL volume attached
to it, the deployment fails when adding the hosts to cluster because it tries to add both the volumes to
the cluster using the same name.
Resolution/Workaround: When creating service deployment with a cluster and hosts, a single volume
should be created and each host should be related to the same volume to be shared. Each host should
not have its own volume created.
Issue: [ASM-1553] In the Resources page, the service tag displayed for the Dell 8/4 FC SAN switch in the
Resource ID column is incorrect.
Description: For the Dell 8/4 FC SAN switches, the asset tag or service tag is not displayed in the
Resource ID column. The unique device identifier will be displayed in the Resource ID column.
However, the device identifier is not the service tag of the device.
Resolution/Workaround: Identify the device using the unique device identifier.
Issue: [ASM-1549] For EqualLogic storage, the volume size displayed in the Storage Group Details page
is slightly higher (2 – 7 GB) than the actual size.
Description: During discovery, volume sizes inventoried are displayed slightly higher than the actual
volumes in the EqualLogic. For example, a volume created as 110 GB is displayed as 112GB.
Resolution/Workaround: See the EqualLogic console for the correct volume size.
Issue: [ASM-1525] Virtual Machines (VM) cannot be added to the expected network on vCenter
(VMkernelPort).
Description: Create a template that contains components from storage to virtual machine. On the
virtual machine, select a private network in the Network Settings section. Private network displays as
VMkernel port in the vCenter. Virtual machine is not added to VMkernel port.
Issue: [ASM-1590] Issue deploying Hyper-V because of incorrect NPAR setting from ASM.
Description: The Hyper-V cannot be deployed to a server if NPAR is enabled. Currently, ASM hardware
configuration does not change the mode from partitioned mode to single function mode. Hyper-V
deployment requires NIC to be configured in single function mode. When the NICs are viewed in
Windows, you will see up to 8 NICs instead of 2 NICs, which the expected.
Resolution/Workaround: Before running the deployment, configure the Fabric A NICs to single function
mode. Update the template for config.xml. This file name is default.erb. Using a text editor with sudo
rights, navigate to /etc/….,find the line for “ “, and change “None” to “NONE”.