Release Notes

Resolution/Workaround: None. Currently, ASM does not enforce license count. Therefore, resources
should still function normally even if a warning message is displayed on the ASM UI.
Issue [ASM-1568]: EqualLogic IP deployment fails at vCenter cluster.
Description: The deployment fails if the iSCSI storage volume authentication method is set to IP/IQN
when deploying ESXi.
Resolution/Workaround: Use only CHAP authentication for EqualLogic deployments.
Issue [ASM-1567]: Deploying EQL iSCSI with IP address does not validate for DHCP network.
Description: Create an EQL volume using IP/IQN address, instead of CHAP, and do not specify a static
network for the SAN iSCSI network. The ESXi deployment fails and the following error message is logged
in the exception.log file.
#<NoMethodError: undefined method `[]' for nil:NilClass>
Resolution/Workaround: Any iSCSI network should be specified with static IP addresses. In addition,
ESXi deployments require EqualLogic with CHAP addressing.
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 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-1928]: Virtual MAC addresses are not updated in resource lists after booting from SAN
deployment.
Description: During booting from SAN deployment ASM configures virtual identities on a server. After
the service is deployed if those servers are viewed in inventory, the old MAC address is displayed, not
the new virtual identities.
Resolution/Workaround: If accurate virtual identities information is required for the server, run
inventory by power cycling the server and run the inventory again through ASM. Alternatively boot the