Release Notes

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.