VMware vCenter Application Discovery Manager 6.1 Release Notes

vCenter Application Discovery Manager 6.1 | 19 AUGUST 2010 | Build 6060

Last Document Update: 19 AUGUST 2010

VMware vCenterTM Application Discovery Manager (ADM), powered by nLayers® provides infrastructure for real-time dependency driven change, configuration, incident, and problem management. Through the ADM's embedded, real-time database, enterprises can accurately manage change impact, control configuration drift, and correlate how infrastructure incidents affect applications.

The database of ADM provides an automated dependency catalog that allows enterprises to eliminate their reliance on tribal knowledge and speculation, and avoid change-induced service outages, degradations, and failures. Enterprises can detect, log, and report the software and hardware configuration changes, and compare configurations server to server. With its native EMC Ionix integration, you can quickly correlate infrastructure incidents to application impact based on real-time models of application topologies and dependency relationships.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • This is a platform migration release that supports the following:
    • Virtual Appliance (VA) deployed on VMware ESX/ESXi 3.5 and later servers.
    • Physical appliance based on IBM 3250 server, backward compatible for 6.0.x hardware.
    • You can deploy ADM using a mixed environment of these platforms.

  • The new Appliance Management platform is easier to use. For more information, see the ADM Administration Guide.

  • ADM now supports the Windows Collector component on Windows 2008 R2 for Virtual Appliances and Windows XP Professional for physical appliances.

  • Support for SFTP transfer for ERDB synchronization.

  • Support for Microsoft Internet Explorer 6 and later versions.

  • Server counting algorithm is enhanced so that ADM detects servers and customizes them more accurately.

  • All of the upgrades are now performed only through the command-line interface. The feature to upgrade from the ADM UI is removed.

  • The LicenseFileGenerator.jar licensing generator is removed and replaced with the VMware licensing mechanism.

  • Only Oracle version is supported for upgrade from ADM 6.0.x to ADM 6.1. Verify the version before upgrading.

Known Issues

  • The build number in ESX console is updated only after a reboot and not after an upgrade.

  • After changing the appliance IP address, the IP address that appears in the ESX console does not change. To reflect the changed IP address, restart all services.

  • Database restore fails if database backup file names start with a hyphen (-).

  • File descriptors leakage leads to a software stability issue.

  • To find a host when using the Search option, you must select the last Detail Discovery result window.

  • Large amounts of unfiltered data can cause delays in ADM report generation. To workaround, use ERDB to handle these large data sets. For more information, see the ADM Repository Reference Guide.

  • An illegal seek string can appear after successful upgrade, but this string has no known impact on system performance.

Resolved Issues

  • The Apache and Sendmail services are up and runs on the Collector virtual machines.

  • The OVF deployment does not take into consideration the swap partition disk space. So, in case of mismatch see the ADM Administration Guide for more information.

  • For better performance, deploy a single Aggregator appliance that includes database instead of deploying a virtual machine database appliance.