VMware

VMware vCenter Application Discovery Manager 6.1.1 Release Notes

vCenter Application Discovery Manager 6.1.1 | 13 DECEMBER 2010 | Build 0057

Last Document Update: 13 DECEMBER 2010

VMware vCenter TM Application Discovery Manager (ADM), powered by nLayers®, provides infrastructure for real-time dependency driven change, configuration, incident, and problem management. Through the embedded, real-time database of the ADM enterprises can 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 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 correlate infrastructure incidents to application impact based on real-time models of application topologies and dependency relationships.

vCenter Application Discovery Manager 6.1.1 is a maintenance release that resolves issues identified in previous ADM releases in addition to offering three new features.

What's in the Release Notes

The release notes cover the following topics:

What's New in this Release

vCenter Application Discovery Manager 6.1.1 provides the following new features:
  • Ability to discover VMware vSphere 4.1
    ADM now supports the discovery of VMware vSphere 4.1.

  • Ability to discover Serial Number and System Universal Unique Identifier (UUID)
    ADM now discovers the Serial Number and System UUID of the target host along with other host attributes.

  • Support for virtual IP Cluster Tolerance
    Network virtualization situations, such as clusters and load balancers, use shared IP addresses. ADM 6.1.1 introduces virtual IP Cluster Tolerance, a feature that solves erroneous data merges from multiple hosts assigned to the same IP or secondary IP into a single host representation in a clustered environment. Cluster tolerance in ADM is tested only on Microsoft Windows 2003 and 2008 cluster setup.

Resolved Issues

This section lists the issues that have been resolved in this release.
  • The URL attributes of IIS service cannot be viewed
    An entry in the flat_property table contains characters that cause the screen to refresh while trying to expand IIS attributes.

    This issue is fixed by GUI rendering.

  • Changes in configuration file values after Detail Discovery does not appear in ADM GUI
    If two or more active discovery policies with same protocol is defined on the same host, then the data retrieved by probing the host with each one of the policies is saved in the discovery schema unless aging is defined on this host. When we merge these data sources into one result, the merge algorithm sorts all the discovery sources by priority. The policies with same protocol have the same priority, so the sort order between them is random. For this reason, the algorithm selects data from old discovery source over newer discovery source.

    This problem occurs if you first change the configuration of the host and discover the host using a Detail Discovery policy. You then have to change the configuration again and rediscover the host with a different Detail Discovery policy. The updated configuration changes and the merged result of the Detail Discovery policy are not displayed in sequence.

    This issue is fixed by sorting and merging the Detail Discovery result according to the last discovery time. This ensures that the latest discovered data is merged.

  • VI SDK discovery does not discover host name
    If you run discovery on the ESX/ESXi machines using VI SDK protocol, it discovers the display name but not the host name of the virtual machines.

    This issue is fixed if you set the name of the virtual machine as the host name and this results in discovery of the host name.

  • Listener stops responding as a result of non-ASCII characters in network traffic packets.
    This fix discards network traffic packets with non-ASCII characters is implemented. With this fix, the probe does not write to the bam file properties with non-ASCII characters. After upgrading to 6.1.1, you need to delete the current bam file or you have to fix the bam file manually by deleting the properties that have non-ASCII characters.

Known Issues and Limitations

This section lists the known issues and limitations for this release.
  • The SSH discovery protocol does not discover the IP address of the virtual machines running on the ESX/ESXi hosts and also does not discover the IP address inside the virtual system settings.

    Workaround: Discover the IP address of the virtual machines using VI SDK protocol on ESX/ESXi machines.

  • System UUID is not discovered for Linux hosts that do not have a dmidecode.

  • For Linux systems, Serial Number and System UUID is discovered only if the user has root permissions.

  • ADM does not discover Serial Number and System UUID on network devices like switches and routers.

  • The Detail Discovery on Solaris and AIX machines does not discover System UUID.

  • The SNMP protocol does not discover the Serial Number and System UUID on any of the hosts.

  • For some specific Windows 2008 configurations, IP addresses and Detail Discovery result of the hosts are not merged as expected.

  • If an IP address is marked as shared IP address by the ADM in a cluster setup and if that IP address is re-assigned to any other network element in the network, then that network element is not discovered.

    Workaround: Perform Restart Discovery and then perform Detail Discovery on that IP address.