VMware

VMware vCenter Infrastructure Navigator 2.0.0 Release Notes

VMware vCenter Infrastructure Navigator Version 2.0.0 | 29 November 2012 | 890698

Last Document Update: 29 November 2012

This release note describes the following topics:

Introduction to vCenter Infrastructure Navigator

VMware vCenterTM Infrastructure NavigatorTM is an application awareness plug-in to vCenter Server, and provides continuous dependency mapping of applications. vCenter Infrastructure Navigator offers application context to the virtual infrastructure administrators to monitor and manage the virtual infrastructure inventory objects and actions. Administrators can use vCenter Infrastructure Navigator to understand the impact of change on the virtual environment in their application infrastructure. vCenter Infrastructure Navigator helps virtual infrastructure administrators perform the following tasks:

  • Make accurate first-level triage to help either eliminate the problem or associate the problem with the virtual infrastructure when business service users report problems.
  • Assess change impact. Manage and communicate virtual infrastructure issues for critical applications.
  • Understand the application and business impact of changes to the virtual infrastructure on applications.

The Open Source Licenses (OSL) file for the virtual appliance is available at /root/open_source_licenses.txt. You can retrieve the file by running the scp root@<appliance IP>:open_source_licenses.txt command.

vCenter Infrastructure Navigator is supported on vCenter Server 5.0 update 1 and vCenter Server 5.1 with the vSphere Web Client 5.1. The user interface of the vCenter Infrastructure Navigator 2.0 virtual appliance that is deployed on vCenter Server 5.0 can only be viewed from the vSphere Web Client 5.1. Apart from all builds of ESXi 5.x version following ESX/ESXi versions are supported.

  Server ESX (ServerPkg) ESXi (VMvisorPkg)
3.5 P25 391406, 437453, 604481, 702112, 725354, 725378

408533, 634899, 634900, 702903, 726914, 726917

409724, 630714, 630715, 702539, 702904, 726915, 727049

4.0.0 U3

398348, 398350, 480973, 480974, 504849, 504850, 538074, 660575, 660580, 702116, 702117, 721907
721909

403553, 481212, 481518, 523312, 523313, 540755, 540756, 660861, 660869, 703609, 703665, 728611
728612

403554, 403555, 481180, 481213, 523315, 523318, 660862, 660870, 702894, 702895, 728607, 728608

4.1.0 P03

433742, 449664, 477600, 477631, 502767, 502790, 538356, 538358, 582267, 582832, 659050, 659051
702113, 702114, 721871, 721872

433803, 449808, 502847, 502854, 544764, 544767, 582837, 523955, 584154, 650334, 659759, 659760
702896, 702897, 728620, 728622

433804, 449810, 502848, 502855, 582815, 582819, 583032, 601443, 606757, 661102, 661103, 702956, 702957, 728621, 728623

Features

This section describes the key features for the vCenter Infrastructure Navigator 2.0.0 release.

Simplifies and automates the deployment and the discovery process and manages Application Component Knowledge Base (KB)
  • Offers application context to virtual infrastructure administrators so that they can monitor and manage the virtual infrastructure inventory objects and actions.
  • Discovers and maps application components and dependencies using KBs and presents this information through dependency maps.
Provides vCenter Infrastructure Navigator data for vCenter Server and related solutions
  • Ensures that the application and dependency data is available to the rest of vCenter Server and its various solutions through the vCenter extensibility APIs.
  • Supports SRM integration to set up more focused and accurate site recovery and backup plans.

What's New in this Release

vCenter Infrastructure Navigator provides the following new features:
  • Multi-tier application discovery and mapping
    vCenter Infrastructure Navigator allows you to define multi-tier application pattern and then discovers all of this pattern instances in the vCenter Server. You can then view these application instances maps.

  • Manual application feature
    You can select virtual machines from vCenter Infrastructure Navigator dependencies map and group them with an application name. You can then view these application instances maps.

  • vCenter Operations Manager integration
    vCenter Infrastructure Navigator discovers a set of virtual machines that are correlated as a platform for a multi-tier application by using a user configured application template or static applications, and publishes this information. If you integrate vCenter Infrastructure Navigator with vCenter Operations Manager, vCenter Operations Manager queries and processes this application related information and reports this application correlated group of virtual machines as an adapter-defined application custom group. You can monitor the discovered application custom group as a vCenter Operations Manager object.

Known Issues

The following issues are known to occur in vCenter Infrastructure Navigator 2.0.0 release. Known issues not previously documented are marked with the * symbol.

  • The character "&" is not accepted as part of the Username text box in the Settings tab of the vCenter Infrastructure Navigator home page.

  • If failover occurs in HA and FT environments, it is difficult to predict whether vCenter Infrastructure Navigator can still monitor the virtual machines that have failed over.

  • Some configurations of vCenter Infrastructure Navigator might be present on the ESX hosts and virtual machines that were previously discovered by vCenter Infrastructure Navigator but were removed before performing the uninstall process of vCenter Infrastructure Navigator.

  • Discovery fails on Linux virtual machines where the temporary directory is a symlink and the virtual machine is installed with VMware Tools version 3.5. You can fix this issue by either updating VMware Tools to a more recent version or by not having the temporary directory symlink.

  • At the vCenter Server entity level, the Navigator portlet on the Summary tab and the Application Services tab might take one second to one minute to display information depending on the number of virtual machines and applications running in your environment.

  • After the uninstall process of vCenter Infrastructure Navigator is completed, the uninstall message stating that the uninstall process is complete does not appear unless you manually refresh the vSphere Web Client.

  • When multiple vCenter Severs are working in a SSO mode, you must log in as a domain administrator that exist on all the vCenter servers to view the vCenter Infrastructure Navigator portlets, and dependency maps.

  • If the Windows Management Instrumentation Command-line (WMIC) service is removed or disabled on a virtual machine, vCenter Infrastructure Navigator does not discover any services running on that virtual machine. In addition, the vSphere Web Client displays an Access failed. Unable to run 'wmic' command on the guest operating system message.

  • vCenter Infrastructure Navigator carries out the discovery process appropriately only if the free disk space available on each of the discovered virtual machines is greater than 5MB. vCenter Infrastructure Navigator displays an error message indicating insufficient space, and the discovery process on that specific virtual machine is stopped until the required free disk space is available.

  • vCenter Infrastructure Navigator does not discover all the versions of a specific service. See vCenter Infrastructure Navigator User's Guide for a detailed list of supported services and their supported versions.

  • When the vShield Manager 5.0 appliance is discovered, the vCenter Infrastructure Navigator user interface does not display the used ports of the discovered service.

  • IPv6 address format is not supported by vCenter Infrastructure Navigator.

  • When you click Show More Dependencies in the dependency map, a group of virtual machines is expanded and added to the dependency map. However, you cannot collapse the same group of virtual machines by clicking the same button. You need to hide the virtual machines one after the other.

  • vCenter Infrastructure Navigator takes approximately 40 seconds to display the dependency map of a virtual machine with more than 70 dependencies.

  • Sometimes the host name of the vCenter Infrastructure Navigator appliance might not persist across reboots and is reset to localhost.localdomain.

  • In a dependency map, when you click the expand or collapse icon to view the list of services within a virtual machine, the layout of dependency map might change. The virtual machine that you have just clicked might move to a different location within the dependency map.

  • If the host name of the vCenter Server does not have a DNS name, vCenter Infrastructure Navigator displays an error message when it exposes data to the vCenter Server inventory service.

  • After the successful upgrade of vCenter Infrastructure Navigator virtual appliance, the latest appliance version is not updated on the Summary tab of the vSphere Client and vSphere Web Client. The Settings tab of the vCenter Infrastructure Navigator home page and the Plug-in Management page in the vSphere Web Client display the correct version.

  • If an external machine has DNS lookup defined, but does not have reverse DNS lookup defined, the dependency map and dependency tab in the vSphere Web Client does not display the external DNS name, but instead displays the external IP address.

  • Info Panel categorizes all processes with a unique key, process identification (PID), for each entry, but PID is not shown in the Info Panel. As a result, you can see same process name associated with different port or one process name is associated with a list of ports.

  • The length of the DNS name of the external virtual machines might vary from one environment to another.

  • After you deploy vCenter Infrastructure Navigator on a vCenter Server 5.1 that does not have a Fully Qualified Domain Name (FQDN) that is resolvable by the DNS, vCenter Infrastructure Navigator fails to register at the vCenter Extension vService. This issue does not occur on a VCVA because VCVA inserts localhost.localdom as the vCenter Server name.

    Workaround: Type the IP address of the vCenter Server in the vCenter Server name text box and deploy the vCenter Infrastructure Navigator virtual appliance again.

  • In the Dependency Map, if you click the unknown service link before spotlighting a virtual machine, the Dependency Map might become unavailable.

  • Workaround: Log out from the vSphere Web Client and log in again. To prevent this, first spotlight the virtual machine and then click the unknown service link.

  • vShield Edge discovery is not supported because of security provisions limitation.*

  • You cannot start the SRM integration on a vCenter Server where multiple SRM instances are installed because vCenter Infrastructure Navigator supports only one installed SRM instance with the default SRM extension name.*

  • Upgrade from vCenter Infrastructure Navigator 1.0, 1.1, and 1.1.1 version to 1.2.0 or 2.0.0 version is not supported.*

  • VMware signed certificates might get revoked. vCenter Infrastructure Navigator does not check the revocation of the certificates and hence you might not be notified if certificates get revoked. If the certificates get revoked, you can change them manually or contact VMware technical support for assistance.*

  • On some occasions, incorrect message appear in the vSphere Web Client, Access failed. An unknown session error has occurred when no free space is left on the target virtual machine. The correct message that should appear is Disk is Full.*

  • If you have vCenter Infrastructure Navigator virtual appliance deployed on vCenter Server 5.0 and if you upgrade vCenter Server 5.0 to vCenter Server 5.1, you must restart the vCenter Infrastructure Navigator virtual appliance.*

  • The inventory table might take few minutes to populate the data depending on the number of related services running in your environment.*

  • Workaround: From the Inventory tree, select an entity with fewer virtual machines.

  • After the upgrade of vCenter Infrastructure Navigator from 1.2 version to 2.0 version, An internal error has occurred - index 0 specified is out of bounds error message is displayed in the vSphere Web Client.*

  • Workaround: Clear the cache of the browser and log in again in the vSphere Web Client.