VMware

VMware vCenter Application Discovery Manager 6.2 Release Notes

vCenter Application Discovery Manager 6.2 | 26 MAY 2011 | Build 0062

Last Document Update: 26 MAY 2011

VMware vCenter TM Application Discovery Manager (ADM) provides infrastructure for dependency driven change, configuration, incident, and problem management. Through the ADM's embedded database, administrators can manage change impact, control configuration drift, and correlate how infrastructure events affect applications.

The ADM database provides a dependency catalog that allows enterprises to eliminate their reliance on speculation, and avoid service outages, degradations, and failures. Enterprises can detect, log, and report the software and hardware configuration changes, and compare configurations server to server. With ADM's native EMC IONIX integration, you can identify impact of infrastructure events on application based on models of application topologies and dependency relationships.

vCenter Application Discovery Manager 6.2 is a minor release that resolves issues identified in earlier ADM releases, and offers some new features listed in What's New in this Release section.

What's in the Release Notes

The release notes cover the following topics:

What's New in this Release

vCenter Application Discovery Manager 6.2 provides the following new features:
  • Ability to authorize and authenticate Active Directory users
    ADM 6.2 supports user authentication over LDAP. Currently, ADM can authorize and authenticate users created in Microsoft Windows Server 2003 Active Directory and Microsoft Windows Server 2008 Active Directory.

  • Ability to discover SharePoint Application
    ADM 6.2 includes the Microsoft SharePoint application as a built-in Application Pattern.

  • Support for NMAP as an additional discovery methodology
    ADM 6.2 uses NMAP as an additional discovery method during IP Discovery. To discover configuration items, you can use NMAP in addition to the existing ICMP and TCP discovery methodology.

Resolved Issues

The following issues have been resolved in this release.
  • In ADM 6.1.1, WMI intermittently fails during discovery with <IP address> was identified as a shared IP error
    This issue is resolved in ADM 6.2. The MAC constraint is checked only if both serial number and UUID is not discovered.

  • ADM is unable to map dependencies based on a few specific ports
    This release includes a new flag called CM, which you can use to reduce the connection maturity time. You can resolve the issue by reducing the connection maturity time from the default one hour to five minutes.

  • After you upgrade ADM, the package lha-1.14i-9.1 is not installed error is displayed
    This issue is resolved in ADM 6.2. The code in ADM 6.2 checks whether the package is installed before trying to remove the package.

  • The unknown section of Discovery MQ Series Fingerprint causes the connection to be shown as peer to peer instead of client to server or server to client
    The unknown section of the MQ Series Fingerprint is removed from the fingerprint.

  • In ADM 6.1, WMI fails during discovery with Unable to write heartbeat file error
    This issue is resolved in ADM 6.2. The watchdog service does not look for the heartbeat file if it is a windows collector.

  • An error occurs while inserting discovery results after you run Detail Discovery using VI SDK protocol to gather information from the vCenter Server
    This issue is resolved in ADM 6.2. The VI SDK protocol does not discover the powered off virtual machines in the vCenter Server.

Known Issues

The following issues are known to occur with ADM 6.2.
  • Cluster Tolerance feature is not supported when you perform discovery with VI SDK protocol. As a result, the discovery fails with insertion errors.

  • ADM is not compatible with Distributed Power Management (DPM) and Disk Raw Mapping (DRM).

  • When you configure Active Directory, ADM does not validate the information in the Domain Name text box.

  • When you add Microsoft Windows Server 2008 Active Directory users, ADM does not validate them.

  • If you perform a database restore on the ADM setup or if you upgrade to a new version of ADM, Active Directory configuration data is deleted.

    Workaround: Reconfigure the Active Directory, if a database restore is performed on the ADM setup or for every upgrade of ADM version.

  • ADM discovers only documented dependency of SharePoint services.

  • SNMP discovers SharePoint services, but does not discover SharePoint attributes and connections.

  • Passive Discovery does not discover SharePoint services.

  • ADM can discover SharePoint services only with Microsoft Windows XP Collector and Microsoft Windows 2003 Collector.

  • In case of a SharePoint distributed setup, ADM discovers documented dependency only if the SharePoint components are discovered in the following order:

    1. Database Server component
    2. Application Server component
    3. Web Front-end component