Active System Manager Release 8.1.
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.1.
What’s New in this Release Active System Manager release 8.1.1 consists primarily of additions to the compatibility matrix in support of Dell Blueprints and Reference Architectures, as well as a new plugin for VMware vRealize Orchestrator that uses the Applications Programming Interface (API) introduced earlier with ASM release 8.1. The highlights of Active System Manager release 8.1.
Fixes This release includes improvements and bug fixes, including previously reported Known Issues that are now resolved, as follows: • ASM-4807 — Resolves an issue where an AD User import fails with the user.name@asm.dell.works.com email format. • ASM-4485 — Resolves an issue where the deployment failed if FC or FCoE deployments PXE are not manually enabled on the first NIC.
• Issue: ASM-2144: Server with bare hard drive fails to get HddSeq set properly o Description: If you choose SD boot and the server has a bare hard drive (not connected through a RAID controller) the HddSeq may fail to get set properly, Leaving the bare hard drive at the top of the list. The server may boot off the bare hard drive instead of the SD card where the operating system was installed.
Unknown error querying ipmi on host 172.31.32.142: Could not retrieve IPMI status: ipmi_sensor_read: internal IPMI error. o • Resolution/Workaround: This is an expected behavior because connection is not established with the BMC for a few seconds when you initiate firmware update operation, and the firmware update continues after the connectivity is established with BMC. Issue: ASM-3133: ASM performs the discovery operation on the FX2 chassis after you update the CMC firmware.
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: Upgrade iDRAC firmware to 2.15 or later. For servers which are on 2.10.10, validate Target Boot Device and RAID Configuration are configured prior to deployment. • Issue: ASM-4273: Volumes deleted from a HyperV service in ASM are not removed completely from the HyperV host. o Description: If you delete a storage volume from a HyperV service, the volume will be deleted on the storage array and removed from ASM service, but there may be stale references left on HyperV hosts.
• Issue: ASM-4453: When you add a server using "Add Resource" to a service the UI is missing the option to select "Management IP Source". o Description: In ASM 8.1.1, when you add a server, ASM user interface does not have the option to choose the "Management IP Source". Resolution/Workaround: None. • Issue: ASM-4561: Problems with 7.12 broadcom Firmware. Description: Broadcom NIC firmware 7.12.xx is not compatible with ASM 8.1.1.
• • Issue: ASM-4593: Dell PowerEdge FC830 and PowerEdge R930 servers fail on vm during hyper-v deployment. o Description: Server reboots automatically when creating VM on HyperV server. This happens on Dell Server when Node Interleave is enabled in the server BIOS. o Resolution/Workaround: Disable Node-Interleave in the server BIOS. Issue: ASM-4632: Not able to create a deployment with FX2 servers having Quad Port Card in Integrated Slot and FC Card in Chassis Slot 8.
• Issue: ASM-5132: On PowerEdge C6320 systems with ESXi version 5.1 or ESXi version 5.2 (update 2), the keyboard is unresponsive if USB 3.0 is set to enabled in the server BIOS. o Description: This issue occurs because USB 3.0 is not supported by ESXi version 5.1 and ESXi version 5.2 (update 2). o 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.
Copyright © 2015 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.
