Release Notes

9
Issue: [ASM-2382] If you duplicate a volume during scale up, volumes are not created.
Description: When you try to duplicate the existing volume during resource scale up, if the volume
does not match with the duplicated resource, the volumes are not actually created.
Resolution/Workaround: During scale up, select the volume that match the resource that is
duplicated.
Issue: [ASM-1891] After changing authentication method from IQN to CHAP in a storage template,
the
CHAP secret is set to default CHAP secret.
Description: While editing a Storage template, if you change the authentication method from IQN to
CHAP, the CHAP secret is set to default CHAP secret in the CHAP secret box.
Resolution/Workaround: In the CHAP secret box, delete the dots, and then enter the actual CHAP
secret.
Issue: [ASM-1928] After Boot from SAN (BFS) service deployment, the Virtual MAC addresses are not
updated for network interfaces.
Description: After successful BFS service deployment, go to the Resources page, click a server that
was deployed, and click View Details in the right pane. In the <resource name> Details page, under
Network Interfaces tab, notice that the Virtual MAC Address and Virtual ISCSI MAC Address are not
being updated.
Resolution/Workaround: To view the newly assigned MAC addresses, go to the respective server
iDRAC device inventory after BFS service was successfully deployed.
Issue: [ASM-2144] If you choose SD card boot
for server deployment, the server deployment times out
if hard drive(s) installed without RAID controllers.
Description: If a service with SD card boot option set and deployed on a server with bare hard drive
or hard drive(s) without RAID controllers, the server deployment times out. ESXi is installed on one of
the hard drives but the server boots up with old operating system installed on the SD card.
Resolution/Workaround: To resolve this issue, either remove the bare hard drives or add RAID
controller to the hard drives.
Issue: [ASM-2368] After initiating a service deployment, while scaling up servers in the service, the
ASM does not lists the server pools that are newly created.
Description: After initiating a service deployment, create one or more server pools. On the Services
page, select the service that you have initiated, and click View Details. In the <service name>
Details page, under Resource Actions, from the Add Resources drop-down menu, click Servers to
add one or more servers to the service. In the Add Server (s) dialog box, notice that Server Pool
drop-down list does not display the newly added server pools.
Resolution/Workaround: <Need Inputs>