Active System Manager Version 7.5.
Copyright © 2014 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.
Contents About This Release ................................................................................................... 4 Active System Manager Release Lineup and Dependencies .................................................... 4 Supported Virtualization Platforms ................................................................................ 4 Supported Client Platforms .........................................................................................
About This Release The release notes contains important information available at the time of release of Active System Manager™(ASM), release 7.5.2, including information about Active System Manager release lineup and dependencies, Active System Manager documentation lineup, known issues, and the methods to contact your service provider. Read through the release notes before installing and configuring your software, and then periodically thereafter for the most up-to-date information.
Supported Client Platforms The following client platforms are supported for this release: • Windows 2012 • Windows Server 2012 R2 • Red Hat Enterprise Linux 6.5 • CentOS 6.
Known Issues The following section lists the known issues with the Active System Manager (ASM) 7.5.2: Issue [ASM-1184]: Unable to launch management interface for blade switches through ASM GUI. Description: After discovering a Dell PowerEdge M1000e chassis, in the Resources page, click the chassis, click View Details, and then click I/O Module Details tab in the Chassis Details page.
Issue [ASM-1093]: While using Active Directory, ASM displays a message “An unexpected error has occurred on the system. Please try again later”. Description: This error occurs if invalid long values are used in the fields during Active Directory instance creation. Resolution/Workaround: None Issue [ASM-1089]: The Phone number field does not allow special or alphabet characters. Resolution/Workaround: While creating a user and entering the value for a phone number, use only numeric characters.
Issue [ASM-1012]: Service description should not contain more than 1024 characters. Description: You cannot deploy a service if a service description is more than 1024 characters. Resolution/Workaround: Make sure that service descriptions do not contain more than 1024 characters. Issue [ASM-956]: Unable to deploy service in some cases where specific NIC or BIOS settings are required. Description: The service cannot be deployed for incorrect BIOS or NIC settings.
Resolution/Workaround: You cannot use “ASMLOCAL” for the imported domain name. Issue [ASM-1240]: Unable to log in to Active System Manager (ASM) with the credentials of the users imported from Active Directory when certain Bind DN formats are used. Description: While creating a directory service to import Active Directory users, the only format used for the “User Name (Bind DN)” value is @. For example, administrator@dell.com.
deployment. Resolution/Workaround: Make sure that any default template is cloned, and then passwords are updated for the new template. Issue [ASM-1198]: Issue while provisioning virtual machines with hostname that has already been used. Description: If you provide the same name of the virtual machine which exists for an earlier deployment to vCenter, even if it does not exist anymore, virtual machines cannot be provisioned.
the samba-client, the full ISOs are required. Issue [ASM-1463]: If you select ESXi 5.5 operating system to deploy Compellent FC storage component, the service cannot be deployed. Description: Currently, ASM supports Compellent 6.3 and ESXi 5.5, but officially ESXi 5.5 support is provided for Compellent 6.4. While creating Compellent components for ESXi 5.5, you must select ESXi 5.1. If you select ESXi 5.5, service cannot be deployed. After selecting ESXi 5.
Issue: [ASM-1576] Need to set vSwitch from beacon probing to "link status only" when using only two NICs. Description: When two physical NICs are used on a vSwitch, beacon probing should be disabled and the setting should be set to "link status only". It is recommended to use beacon probing only when you have three or more network adapters. Resolution Workaround: In vCenter, for a host configuration, go to vSwitch properties and change the settings for each vSwitch and port group to “Link status only”.
Issue: [ASM-1564] A cluster cannot be deployed when multiple storage volumes are added to a cluster. Description: When creating a template that has two servers and each had a single EQL volume attached to it, the deployment fails when adding the hosts to cluster because it tries to add both the volumes to the cluster using the same name.
Issue: [ASM-1594] Template page does not loads properly after you restart the ASM appliance when SCVMM offline. Description: After discovery of an SCVMM instance, create an SCVMM cluster component that uses the discovered SCVMM instance. If you restart the ASM appliance when SCVMM instance is offline, the template page may stops responding. Resolution/Workaround: Bring the SCVMM instance online to load the template page properly.
Active System Manager Documentation Lineup The current lineup of the Active System Manager product guide documentation for this release includes the following: • Dell Active System Manager Version 7.5 User’s Guide — Provides an overview of Active System Manager, the detailed information about using the Active System Manager graphical user interface (GUI) and information to troubleshoot Active System Manager. • Dell Active System Manager Version 7.
