Dell Active System Manager Version 7 5 Owners Manual 7.5.1 Release Notes

: Dell Dell-Active-System-Manager-Version-7-5-Owners-Manual-117283 dell-active-system-manager-version-7-5-owners-manual-117283 dell pdf

Open the PDF directly: View PDF .
Page Count: 11

Active System Manager

Version 7.5.1

Release Notes

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 ........................................................................................... 5

Active System Manager Web Interface Platforms ................................................................. 5

Known Issues ............................................................................................................. 5

Active System Manager Documentation Lineup .................................................................. 11

Contacting Technical Support ...................................................................................... 11

About This Release

The release notes contains important information available at the time of release of Active System

Manager™(ASM), release 7.5.1, 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.

This Active System Manager documentation includes:

• About This Release

• Active System Manager Release Lineup and Dependencies

• Known Issues

• Active System Manager Documentation Lineup

• Contacting Technical Support

Active System Manager Release Lineup and Dependencies

The following topics outline Active System Manager release lineup and dependencies for Release 7.5.1:

• Active System Manager Software Components

• Supported Virtualization Platforms

• Supported Client Platforms

• Active System Web Interface Platforms

Active System Manager Software Components

Active System Manager components that form this release include:

• ASM 7.5.1 Virtual Appliance

Supported Virtualization Platforms

The following virtualization platform is supported for this release:

• VMware ESXi 5.1

• VMware ESXi 5.5

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.5

Active System Manager Web Interface Platforms

The following Web Interface Platforms are supported for this release:

• Microsoft Internet Explorer, version 9 and later

• Mozilla Firefox, Version 26.0 and later

• Google Chrome, Version 32 and later

• Safari, version 6 and later

Known Issues

The following section lists the known issues with the Active System Manager (ASM) 7.5.1:

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. This tab

shows a list of I/O Modules that contains links for the Management IP, which is not correctly launching

the management interfaces for these resources.

Resolution/Workaround: None

Issue [ASM-1152]: Unable to deploy a service using a template that contains more than one vCenter

cluster.

Description: If a template contains two clusters in the same vCenter instance, the service cannot be

deployed.

Resolution/Workaround: While deploying a service using a template, make sure the template contains

only a single vCenter Cluster.

Issue [ASM-1151]: CentOS is deployed successfully but ASM GUI displays a message that the

deployment is unsuccessful.

Description: Duplicate host names can cause this issue because the remote host operating system

checks the deployment with its host name. If an earlier host with a different service tag has checked in

with the same host name, the host name is not registered because the name already exists. If you

delete an earlier deployment, always use a unique host name.

Resolution/Workaround: Always use a unique host name.

Issue [ASM-1147]: If you delete a network that is used in a published template, the template remains

in the published state. However, the service cannot be deployed using the template.

Description: ASM will allow you to delete a network even if it is used in a template. If you attempt to

deploy a template with a deleted network, the service cannot be deployed.

Resolution/Workaround: Make sure that all the networks in the published template exist in ASM.

Issue [ASM-1134]: You cannot deploy the service if an ESXi host has iSCSI storage volumes attached

additionally, which is beyond the limit that ASM can deploy.

Resolution/Workaround: Before you deploy a host, make sure the host does not have storage that has

been provisioned already or you can review the access credentials on your storage array.

Issue [ASM-1122]: vSwitch created on servers with 1 GB NICs do not tag ports correctly.

Description: 1 GB NICs is not supported.

Resolution/Workaround: None

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-1051]: You cannot select vNICs associated with vSwitches in VMware vCenter.

Description: During deployment of ESXi, vSwitches created by ASM do not allow you to select vNICs

because the vNICs are selected by ASM.

Resolution/Workaround: None

Issue [ASM-1013]: If you specify a Storage Pool that does not exist, a message indicating an error is

displayed

.

Description: After creating a storage template, if you type a Storage Pool name that does not exist

then the deployment indicates an error.

Resolution/Workaround: None

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 may have to update the settings in a config XML file for the server.

Issue [ASM-953]: SD Card Mirroring must be enabled on all the physical servers.

Description: The deployment to bare metal server do not consider dual SD card. Thus ASM could deploy

the operating system in one SD card and boot from the other. Servers are shipped from the factory with

appropriate settings.

Resolution/Workaround: If this issue occurs, make sure that SD card mirroring is enabled on the

server.

Issue [ASM-836]: If you delete a user in Active Directory, the user still exists in ASM Users list.

Description: If an Active Directory user is already imported to ASM and the user is deleted in Active

Directory server, you can no longer log in again. The user exists in the ASM Users list and can still edit

the details about the user. If you add the deleted user in Active Directory again, you must log in using a

new password.

Resolution/Workaround: None

Issue [ASM-837]: The group a user belongs to in Active Directory is not associated with the role that the

user must be associated in ASM.

Description: A user under a group in Active Directory is not associated with the role that the user must

be associated in ASM. A non-administrator user can be assigned the Administrator role in ASM.

Resolution/Workaround: Make sure that during import of Active Directory users, appropriate ASM role

level is assigned.

Issue [ASM-685]: Inventory of EqualLogic storage may be incomplete.

Resolution/Workaround: Make sure that EqualLogic storage array is configured with a “public” SNMP

community name.

Issue [ASM-546]: System time out does not occur if any of the pages that list the information is open.

That is, Resources page, Templates page, and so on.

Resolution/Workaround: If you are on a page that displays a list view, make sure you close these pages.

Issue [ASM-1150]: Importing users from Active Directory blocks access for local users.

Resolution/Workaround: You cannot use “ASMLOCAL” for the imported domain name.

Issue [ASM-1182]: After deploying an application, the actual state of deployment is not reflected. After

informing the Resource Module Agent, the status shows Complete. But the users do not know whether or

not the application is deployed.

Description: If you deploy a template that includes an Application, the service is deployed and ASM

displays status as Complete. But the application is not deployed. The Application will take no longer

than 30 minutes to deploy. The user should manually confirm whether or not the applicatio

n is deployed

successfully.

Resolution/Workaround: None

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 <user>@<domain>. For example, administrator@dell.com. If any

other formats are used, you can import users, but users cannot log in to ASM.

Resolution/Workaround: If users have already been imported, delete the users. Edit the directory

service “User Name (Bind DN)” and use the format <user>@<domain>, and then re-import users.

Issue [ASM-1243]: While importing user from Active Directory (AD), an error message is displayed,

indicating user already exists.

Description: If you add the same user accidently one or more times by clicking the Add button more

than once. After adding the same user multiple times, if you click Apply to apply the new settings, an

error message is displayed indicating user already exists.

Resolution/Workaround: Close the Import Active Directory Services dialog box. Check whether or not

the user was successfully added. If the user was not added, open the Import Active Directory Services

dialog box and the user again. Make sure that you add the user only once.

Issue [ASM-1227]: The Edit Directory Services dialog box displays incorrect information about the

protocol used for Active Directory (AD) services. The Plain protocol is always displayed, even if the

service is set to SSL.

Description: While editing an Active Directory (AD) service, the Edit Directory Services dialog box

always displays the Plain protocol, even if the directory service is set up and uses SSL

protocol. This can

cause issues when importing Active Directory users for this service.

Resolution/Workaround: To make sure the correct setting, for SSL simply select SSL and save the

directory service settings, and then re-import users. If you want to use Plain protocol, first set the

protocol to SSL, and then from the drop-down list select Plain protocol. After selecting the protocol,

save the settings, and then re-import users. Therefore, the correct protocol is used, even if ASM GUI

does not display correct protocol.

Issue [ASM-1223]: ASM displays incorrect information about EQL storage details. Storage pool

information is not accurate.

Resolution/Workaround: Make sure that information about storage pools is retrieved from actual

EqualLogic Management GUI for the storage being managed.

Issue [ASM-1352]: After restoring a backup, non-ESXi repositories are not restored. The service cannot

be deployed until you manually re-create repositories.

Description: After you restore a backup to an ASM virtual appliance, the backup cannot re-create OS

installation repositories. The service cannot be deployed using non ESXi-OS after restore until you

re-create their OS repositories in Razor.

Resolution/Workaround: After performing a restore, make sure all OS install repositories are re-

created.

Issue [ASM-1291]: If the configure components are not selected in correct order in a template, the

information is not saved successfully.

Description: If you do not update the template components in the appropriate order then information

and settings that you enter in a template are not saved successfully.

Resolution/Workaround: Create a template starting with dependent items first. For example, when

you

create a template with storage, server, and cluster components, makes sure to create the storage

component, then the server component, and finally the cluster component.

Issue [ASM-1260]: An operator cannot delete an unsuccessful service deployment.

Description: An operator can initiate a service deployment, but ASM does not provide the ability for an

operator to delete that service. The Delete button is greyed out.

Resolution/Workaround: Only an admin user can delete a service that is failed.

Issue [ASM-1255]: Default template passwords are not displayed, and the users are not prompted to

change the password.

Description: Default templates that ship with ASM appear to contain passwords because a masked value

is visible in password fields. Actually a password is not present, so this causes issues during service

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 virtual

machine is created on vCenter, but the OS cannot be installed on the virtual machine and virtual

machines are not provisioned indicating an error.

Resolution/Workaround: You cannot use the same virtual machine name on subsequent deployments.

Issue [ASM-1196]: The Windows unattend file contains a clear text password.

Description: The Windows unattend.xml.erb file contains a clear text password. This password is

required for razor to install Windows. It is accessible through the svc URL, which should be isolated on

the PXE network.

Resolution/Workaround: You should make sure that the password is changed after the Windows install

or set to Windows to force you to change password on first login.

Issue [ASM-1086]: Active Directory user import displays an error message if the name contains invalid

characters.

Resolution/Workaround: Make sure while importing the Active Directory user name, the user name

contains only alphanumeric characters.

Issue [ASM-1055]: After configuring networks for vSwitch on ESXI, all dialog boxes display UUIDs.

Description: While deploying a service, the dialog boxes in the Service Recent Activity display UUIDs

instead of actual network names.

Issue [ASM-1001]: Unable to deploy a service for Fiber Channel storage component if the server object

is already mapped to the volume in Storage Center.

Description: If the server object is already mapped to a volume in Compellent Storage Center then a

service cannot be deployed for storage component.

Resolution/Workaround: Un-map the volume in Compellent Storage Center, and then retry the service

deployment.

Issue [ASM-1469]: Unable to deploy a Resource Module using CentOS 6.5 because devices do not check

in using ASM.

Description: ASM installs an agent in the deployed operating system using a CIFs share, and this agent

should check in to confirm the deployment. If the minimal ISO is used on CentOS, the correct packages

for the samba-client to mount the share are not included. Therefore, the agent RPM cannot be

downloaded.

Resolution/Workaround: To install CentOS, do not use the minimal install because this does not include

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.1 for the storage

component, the Compellent server objects are created using ESXi 5.1. The settings for ESXi 5.1 and ESXi

5.5 are functionally the same, and the deployment works.

Resolution/Workaround: If you want to deploy a Compellent storage component using ESXi 5.5, in the

Template Builder page, select VMware ESXi 5.1 from the Operating System Name drop-down list for

the storage component.

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.5 Online Help — Provides detailed information about

using the Active System Manager graphical user interface (GUI). You can access the Online Help

from the ASM interface.

• Dell Active System Manager Version 7.5 Quick Installation Guide — Provides detailed

information about installing Active System Manager (ASM) in your environment and configure

the virtual appliance that hosts ASM.

• Dell Active System Manager Version 7.5.1 Release Notes — Provides a summary of the latest

Active System Manager features, software changes, and system requirements, and the

customer-facing known issues unique to each particular release.

For the latest documentation for Dell Active System Manager, version 7.5:

1. Go to dell.com/support

2. On the Support page, in the Select a product section, click Software & Security.

3. In the Software & Security section, click the required link from the following:

a. Client System Management

b. Enterprise System Management

c. Remote Enterprise System Management

d. Serviceability Tools

4. To view the document, click the required product version.

NOTE: You can also directly access the documents using the following links:

• For Client System Management documents — dell.com/OMConnectionsClient

• For Enterprise System Management documents — dell.com/openmanagemanuals

• For Remote Enterprise System Management documents — dell.com/esmmanuals

• For Serviceability Tools documents — dell.com/serviceabilitytools

Contacting Technical Support

The level of support that Dell provides is based on your support maintenance contract. Contact Dell

technical Support by visiting the Dell web site at http://www.dell.com/support/softwarecontacts.