Release Notes

Description: The chassis firmware update triggers the chassis inventory which triggers the chassis discovery to detect any newly
inserted blades or IOMs.
Resolution/Workaround: This is an expected behavior. When you update the CMC firmware on the PowerEdge FX2 chassis, the
chassis firmware update operation initiates the chassis inventory operation, which in turn initiates the chassis discovery operation to
collect the information about the blades or IOMs that are newly inserted.
• Issue: ASM 3490: Host and sub host groups cannot be used in separate deployments for the Hyper-V deployments.
Description: 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.
Resolution/Workaround: None
• Issue: ASM-3545: C-series cannot be taken as a reference server though it is displayed in the import list.
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-3639: Time difference between the installed operating system and ASM appliance may cause the operating system post-
install configuration on servers and virtual machines to fail while waiting for puppet agent to check in.
Description: ASM includes a puppet agent while installing the Windows or Linux operating systems. The puppet agent communicates
with the ASM appliance to retrieve the post-install configuration and both server (ASM), and client-side SSL certificates are checked
for validity during this process. The ASM server-side SSL certificate is created when the ASM appliance is first started and is marked
valid only after the first boot time of the appliance. Hence, a failure may occur if the initial time set on the appliance is incorrect.
To view this issue, manually run the "puppet agent -t" command on the server or VM that is experiencing a failure. This problem
usually results in SSL_connect errors in the output, and the following message is displayed: CRL is not yet valid for /CN=dellasm.
Resolution/Workaround: Ensure that the hypervisor host on which you want to install ASM is set to the correct time and NTP is
used for the ASM appliance, ASM installed servers, virtual machines to ensure consistency in the time.
• Issue: ASM-3862: UEFI boot is not supported in ASM.
Description: The BIOS boot mode does not change to UEFI after the local hard drive is set as the target boot device. This issue
occurs because ASM does not support UEFI boot support.
Resolution/Workaround: None
• Issue: ASM-4205: ESXi 6.0 with Dell Compellent fails if the array has firmware version later than v6.6.
Description: vCenter 6.0 support is added with Storage Center 6.6. While creating a deployment with ESXi 6.0, select Dell
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 Dell Compellent Storage
component, select Operating System as "ESXi 5.5" or "ESXi 5.1".
• Issue: ASM-4273: Volumes deleted from a Hyper-V service in ASM are not removed completely from the Hyper-V host.
Description: If you delete a storage volume from a Hyper-V service, the volume is deleted on the storage array and removed from
ASM service, but there may be stale references left on the Hyper-V hosts.
Resolution/Workaround: Manually remove references to non-existent volumes in Hyper-V using disk manager.
• Issue: ASM-4328: After restore, operating system and firmware must be able to be rebuilt.
Description: After a restore, operating system and firmware repositories are placeholders. The user must now remove the
repositories and add new ones. However, any existing templates or services that rely on the repositories prevent the existing
repositories from being deleted to be re-added. Hence, the user must change the repositories for all templates, and any existing
services have to be deleted to point to the correct repository.
Resolution/Workaround: For any repositories, they cannot be used for new templates or as an option for adding resources to a
service, and provide a method to rebuild the existing repository without requiring deletion.
• Issue: ASM-4561: Problem with 7.12 Broadcom firmware
Description: Broadcom NIC firmware 7.12.xx is not compatible with ASM. It can cause intermittent connectivity issues which results
in hypervisor and bare metal OS deployment failures.
Resolution/Workaround: Apply the firmware available in the latest ASM catalog. Alternatively, manually downgrade your Broadcom
NIC firmware to 7.10.xx. Also, note that v7.12.17 will not work and later versions resolves this issue, but 7.10.xx is the qualified version.
• Issue: ASM-4590: Intel NIC cards must be at version 15.5.0 or later for firmware updates to work.
Active System Manager Release 8.3.1 Release Notes
7