VMware vCenter Infrastructure Navigator 1.0.0 Release Notes

VMware vCenter Infrastructure Navigator Version 1.0.0 | 24 JANUARY 2012 | Build 592384

Last Document Update: 24 JANUARY 2012

These release notes describe the following topics:

Introduction to vCenter Infrastructure Navigator

VMware vCenter™ Infrastructure Navigator is an application awareness plug-in to vCenter Server, and provides continuous dependency mapping of applications. Infrastructure Navigator offers application context to the virtual infrastructure administrators to monitor and manage the virtual infrastructure inventory objects and actions. Administrators can use Infrastructure Navigator to understand the impact of the change on the virtual environment in their application infrastructure. 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.

Infrastructure Navigator is supported on vCenter Server 5.0 with the vSphere Web Client. The supported ESX versions include ESX/ESXi 3.5 (build 425420), ESX/ESXi 4.0 (build 398348), ESX/ESXi 4.1 (build 433742), and all builds of ESXi 5.x.


This section describes the key features for the Infrastructure Navigator 1.0.0 release.

Simplifies and automates the deployment and the discovery process and keeps manages Application Component Knowledge Base (KB) current
  • Eliminates physical switch spanning or credential based discovery.
  • Discovers and maps the application components and dependencies using KBs and presents this knowledge through maps or search for relevant use cases.
Provide Infrastructure Navigator data for vCenter Server and related solutions
  • Ensures that the application and dependency data is available to the rest of the vCenter Server entities and its various solutions through the vCenter extensibility APIs.
  • Supports SRM integration to set up more focused and accurate site recovery and backup plans.

Known Issues

The following issues are known to occur in vCenter Infrastructure Navigator 1.0.0 release.

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

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

  • If you uninstall the Infrastructure Navigator plug-in, you cannot revert the password from the disconnected ESX host and its virtual machines.

  • Infrastructure Navigator does not support VMware vCloud Director (VCD).

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

  • After the discovery starts, the Reconfigure virtual machine task initiated by com.vmware.vadm appears in the vSphere Client for every virtual machine managed by vCenter Server.

  • If you want to clear the Infrastructure Navigator database, you must uninstall the current Infrastructure Navigator appliance and import a new OVA instance.

  • If you deploy a new version of Infrastructure Navigator with a new version of online help, the new version of online help is not updated in the vSphere Web Client.

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

  • Incoming dependencies that were discovered earlier, but no longer exist, remain in Infrastructure Navigator map and portlet, unless you stop or remove their services.

  • After the uninstall of Infrastructure Navigator is completed, the uninstall completion message does not appear unless you manually refresh the vSphere Web Client.

  • The Navigator tab displays an error message when you try to access the dependency map or dependency table of a virtual machine that has dependencies to another virtual machine which is unauthorized for the current vCenter Server user.

  • Infrastructure Navigator does not support non-unique UUID in the virtual machines. If two or more virtual machines with non-unique UUID are present on the ESX hosts that are being monitored by Infrastructure Navigator, the discovery of those virtual machines fails and their status remains as Pending For Discovery.

  • If the Windows Management Instrumentation Command-line (WMIC) service is removed or disabled on a virtual machine, Infrastructure Navigator does not discover any services running on that virtual machine.

  • In a Linked Mode environment, if you disable the Infrastructure Navigator plug-in in any of the vCenter Server instances, the functionality of Infrastructure Navigator gets disabled on all the visible vCenter Server instances.

  • In a Linked Mode environment, if any of the vCenter Server instances, including the ones where Infrastructure Navigator is not being deployed, has non-running inventory services, Infrastructure Navigator does not display maps and tables on the discovered virtual machines. A pop-up appears that states that the information cannot be retrieved from the Infrastructure Navigator.

  • In a Linked Mode environment with multiple Infrastructure Navigator instances on more than one vCenter Server, the license rows of Infrastructure Navigator in the licensing screen of the vSphere Client appear with the same name, and you cannot distinguish which row belongs to which vCenter Server. This might be relevant if you need different licenses for the different vCenter Server instances.

  • In a Linked Mode environment, you must log in as a domain user to view the Infrastructure Navigator dependency maps.