Dell Active System Manager Release 8.3.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Active System Manager Release 8.3.1 Release Notes............................................................................................................4 Release Type and Definition ...........................................................................................................................................4 Platforms Affected.............................................................................................................................................................
Active System Manager Release 8.3.1 Release Notes This document describes the new features, enhancements, and known issues in Dell Active System Manager Release 8.3.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.
New in this Release Active System Manager 8.3.1 is focused on expanding capabilities around the vSAN deployment, adding new capabilities around managing Ready Bundle for Virtualization, and improving the granularity of information shown around the current state of environments under management. The highlights of the Active System Manager release 8.3.1 include the following: • • • • Support for the SATADOM boot option for Dell PowerEdge R630, PowerEdge R730, and PowerEdge R730xd systems.
• ASM-7934—Resolved an issue where a failed server in a cluster deployment prevented the storage DRS configuration from completing until all servers were deployed successfully. Known Issues This section provides information about open issues and resolutions with this release of Active System Manager 8.3.1. • Issue: ASM-1469: The puppet agent fails to install on CentOS v6.4. The CentOS v6.4 cannot mount the appliance's CIFS share to download the rpm.
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.
Description: Firmware update for 12th generation blades with the Intel cards and the 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.x requires a manual update to 15.5.0, prior to upgrading to 16.5.x with ASM. • Issue: ASM-4688: In NIC firmware, the X520/I350 rNDC firmware version 15.0.28 to version 16.5.20 firmware fails to update in the firmware update logs.
Resolution/Workaround: Ensure that you do not assign static networks to the Server (Hardware Only) components or ensure that the static networks that are used have enough IP addresses that can be assigned to the component. • Issue: ASM-6219: Backup and restore may reject valid CIFS share credentials. Description: ASM may reject valid credentials in cases where CIFS shares have anonymous or guest privileges. Resolution/Workaround: Clear the credentials, and retry the operation.
Description: After creating custom bundles, an incorrect time stamp is displayed for the bundles on the View Bundles page. Resolution/Workaround: Set NTP and restart the appliance to fix the issue. • Issue: ASM-8344: PXE boot on a second Intel NIC fails. Description: If you are using a server with two Intel X710 NICs, operating system installation network assigned to the second port fails with the message that the NIC cannot be found.
3. 4. 5. 6. 7. • Select the server object and click Edit. Under Hardware Settings, select Local Hard Drive from the Target Boot Device drop-down box. Under OS Settings, select the Auto-generate Host Name check box. Under Hardware Settings, select Boot From SAN (iSCSI) from the Target Boot Device drop-down box. Publish and deploy the template. Issue: ASM-8734: vDS failure if operating system installation and hypervisor management networks are set on separate ports.
