Active System Manager Release 8.
Release Type and Definition Active System Manager Active System Manager (ASM) is Dell’s unified management product that provides a comprehensive infrastructure and workload automation solution for IT administrators and teams. The release notes contains important information available at the time of release of Active System Manager (ASM) release 8.2, including information about the ASM release lineup and dependencies, ASM documentation lineup, known issues, and the methods to contact Dell technical support.
New in this Release Active System Manager 8.2 is focused on expanding capabilities around workload deployment, adding new capabilities around managing existing environments, and improving the granularity of information shown around the current state of environments under management. The highlights of Active System Manager release 8.
ASM release 8.2 build 5877 is an update to ASM release 8.1.1. It contains fixes and enhancements that include: • • • • • • • • Support to enable or disable local disks while booting the operating system from SD cards for ESXi deployments. Added message prompt in the user interface directing the user to the Firmware Update wizard to rerun a firmware update that is failed in a service.
• • • • • • ASM-4282 — Resolves an issue in HyperV services, where if only the last server is selected for teardown without including the cluster, the host is removed from the cluster. ASM-4399 — Resolves an issue where the testing123 message is displayed when upgrading from version 8.1 to version 8.1.1. ASM-4453 — Resolves an issue where the “Management IP Source” option is not available if you add a server using "Add Resource" to a service.
• Issue: ASM-1894: ASM is unable to distinguish volumes with the same names in different Compellent folders. Description: ASM cannot distinguish volumes with a same name in different folder in a Compellent inventory Resolution/Workaround: Ensure that you provide unique names for volumes used by ASM in your Compellent inventory.
Resolution/Workaround: This is an expected behavior. When you update the CMC firmware on 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-3157: For SCVMM cluster provisioning, Active Directory must not contain any hosts with the same name.
• 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-4123: Service reports "Error" state though all other components are successful.
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 need to be at version 15.5.0 or later for firmware updates to work. Description: Firmware update for 12th generation blades with intel cards and Broadcom card fails in some cases when Intel NICs are installed if it is not of version 15.5.0. Resolution/Workaround: Updating Intel X520 cards with versions earlier than 15.5.0 to 16.5.
Description: This issue occurs because USB 3.0 is not supported by ESXi version 5.1 and ESXi version 5.2 (update 2). Resolution/Workaround: Try any of the following options to resolve the issue: • Disable USB 3.0 from the server BIOS. For servers that require USB 3.0, upgrade ESXi to version 5.5 (update 3) or version 6.0. Issue: ASM-5397: Unable to login to the user interface. Description: The user interface is inaccessible when you login after updating to ASM 8.2.
Resolution/Workaround: As a best practice for all imported templates, clear the password field and set them correctly. • Issue: ASM-6311: Stale Active Directory account entries for HyperV host and cluster can fail HyperV deployments. Description: A HyperV deployment may fail if stale Active Directory account entries corresponding to a host or a cluster name are used in a deployment. Resolution/Workaround: Ensure that you clear the unused and stale entries from Active Directory and then try a deployment.
Copyright © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
