VMware

VMware vCenter Infrastructure Navigator 1.2 Release Notes

VMware vCenter Infrastructure Navigator Version 1.2 | 10 September 2012 | 823962

Last Document Update: 10 September 2012

This release note describes the following topics:

Introduction to vCenter Infrastructure Navigator

VMware vCenterTM 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 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 update 1 and vCenter Server 5.1 with the vSphere Web Client 5.1. You can manage a version 5.0 vCenter Server only through a version 5.1 vCenter Server and a version 5.1 vSphere Web Client. The supported ESX versions include ESX/ESXi 3.5 (builds 425420, 408533, and 409724), ESX/ESXi 4.0 (builds 398348, 403553, and 403554), ESX/ESXi 4.1 (builds 433742, 433803, and 433804), and all builds of ESXi 5.x.

Features

This section describes the key features for the Infrastructure Navigator 1.2 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 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

Infrastructure Navigator 1.2 is a major release and is compliant with the vSphere 5.1 release. If vSphere 5.1 Web Client manages one or more vCenter Server 5.0 instance, then you must have all the relevant machines on the same domain and registered to the SSO server.

Known Issues

The following issues are known to occur in vCenter Infrastructure Navigator 1.2 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 Infrastructure Navigator home page.

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

  • Some configurations of Infrastructure Navigator might be present on the ESX hosts and virtual machines that were previously discovered by Infrastructure Navigator but were removed before performing the uninstall process of 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.

  • The 5.1 version of the vSphere Web Client does not display the Infrastructure Navigator 1.2 online help.

  • At the vCenter Server entity level, the Navigator portlet on the Summary tab and the Application Services tab itself might take anywhere between 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 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.

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

  • 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 for 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.

  • 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 addition, the vSphere Web Client displays an Access failed. Unable to run 'wmic' command on the guest operating system message.

  • 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 5 MB. 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.

  • Infrastructure Navigator does not discover all the versions of a specific service. See 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 Infrastructure Navigator user interface does not display the used ports of the discovered service.

  • IPv6 address format is not supported by Infrastructure Navigator.

  • When you click Show More Dependencies button 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.

  • 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 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, Infrastructure Navigator displays an error message when it exposes data to the vCenter Server inventory service.

  • After the successful upgrade of 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 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 Infrastructure Navigator on a vCenter Server 5.1 that does not have a Fully Qualified Domain Name (FQDN) that is resolvable by the DNS, 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 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 scenario, first spotlight the virtual machine and then click the unknown service link.