Release Notes

HDD and then SD. After the operating system was installed the server was not
able to boot from the HDD.
Resolution/Workaround:
Check for ESXi management IP Address access.
Issue: ASM-3545
: C-series cannot be taken as a reference server though it is displayed in
the import list.
o
Description
: This is an expected behavior. C-series servers cannot be
referenced as reference servers as they do not have iDRAC supported.
Resolution/Workaround
: None
Issue: ASM-3813:
When adding a Firmware Repository from a local drive, user is able to
upload arbitrary files. While this functionality parses this file to verify whether it is either an
XML or CAB file, parsing occurs after the file has already been written to the /tmp directory.
o
Description
: The client(browser) on large file uploads continues to stream
data after the maximum size exception has been thrown and the client
therefore never receives the error response or error messaging that the file is
too large to upload. The following error message is displayed.
Invalid file format: "The upload file format is invalid.
Please verify the format and try again."
Resolution/Workaround
: None
Issue: ASM-3892
: Firmware update for 12th generation blades with intel cards and
Broadcom card fails in some cases when Intel NICs are installed.
o
Description
: Updating Intel X520 cards with versions earlier than 15.5.0 to
16.5.x requires a manual update to 15.5.0, prior to upgrading to 16.5.x with
ASM.
Resolution/Workaround
: None
Issue: ASM-4123
: Service reports "Error" state though all other components are successful.
o
Description
: In some cases when deleting a failed resource, for example, a
VM Component, from a successful servers puts the service in error state
despite all remaining components in successfully "Deployed" state.
Resolution/Workaround
: Retry the service should move the service state
back to successful.
Issue: ASM-4174:
ASM backend not to tear down the shared resources.
o
Description
: When deleting a service the user has the option to delete
clusters and storage. If these are shared with other services, ASM will not
warn the user and will proceed to remove the shared resources.
Resolution/Workaround
: Prior to deleting a service, verify which clusters and
storage volumes are shared with other services. Only select delete for
resources which will not impact other services.
Issue: ASM-4205
: ESXi 6.0 with Compellent will fail if the array has firmware version later
than v6.6.
o
Description
: vCenter 6.0 support is added with Storage Center 6.6. While
creating a deployment with ESXi 6.0, select Compellent for which storage
center is upgraded to version 6.6
Resolution/Workaround
: In case the storage center is running on version less
than 6.6, then for Compellent Storage Component, select Operating System
as "ESXi 5.5" or "ESXi 5.1"
Issue: ASM-4216:
In some cases Boot Order, Target Boot Device and RAID Configuration
are not set
.
o
Description:
Template settings for Target Boot Device and RAID
Configuration are not set even though the deployment is complete and
successful. This only appears to be an issue with iDRAC version 2.10.10.