VMware vCenter Infrastructure Navigator 5.8.2 Release Notes
VMware vCenter Infrastructure Navigator Version 5.8.2 | 24 June 2014
Last Document Update: 15 June 2014
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 that provides continuous dependency mapping of applications. vCenter Infrastructure Navigator offers application context to 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 decisions to help either eliminate a problem, or associate a 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.
Supported VMware Environments
vCenter Infrastructure Navigator is supported on vCenter Server 5.1 U2 and 5.5 U1, with the vSphere Web Client 5.5, or earlier.
In addition to all builds of ESXi 5.x, the following ESX/ESXi versions are supported.
You can view the interoperability matrix by clicking this link.
What's New in this Release
vCenter Infrastructure Navigator 5.8.2 adds support for vSphere 5.5 U1 and 5.1 U2.
The following issues have been fixed in this release.
- The issue in which, in some cases, the vCenter Infrastructure Navigator maps showing relationships between virtual machines do not display and an Error Loading Map error appears has been addressed.
- The issue in which a Pending first discovery message is displayed in the vSphere Web Client, although vCenter Infrastructure Navigator had successfully discovered virtual machines, has been addressed.
The issue in which the Install Hyperic Agent: Unable to execute action. Action timed out during execution. error message is returned when you install a vCenter Hyperic agent using the agent management feature, has been addressed.
The following issues are known to exist in vCenter Infrastructure Navigator 5.8.2.
- The interoperability between supported versions of vCenter Server, vSphere Web Client and vCenter Infrastructure Navigator are described in the VMware vCenter Infrastructure Navigator Installation and Configuration Guide.
To deploy vCenter Infrastructure Navigator on a version of vSphere Web Client that is earlier than version 5.1U1b, scriptPlugin must be disabled in the webclient.properties file. Remove or comment out scriptPlugin.enabled = true.
- From vCenter Infrastructure Navigator version 5.8, you must create a profile for a Hyperic agent, before you can deploy agents to virtual machine. Any Hyperic agent settings that you had set when using vCenter Infrastructure Navigator version 5.7 are no longer available.
- If you upgrade vCenter Server from version 5.1 to version 5.5, you must restart the vCenter Infrastructure Navigator virtual appliance.
- You cannot have more than one instance of MSSQL on a virtual machine. If you do have multiple instances with different versions, for example MSSQL 2010 and MSSQL 2012, on the same virtual machine, both services will be discovered as the latest version.
- When a virtual machine with multiple IP addresses has several services running on the same port, those services are not discovered.
- Non-ASCII characters are not accepted in passwords in vCenter Infrastructure Navigator.
- 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.
- 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.
- 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.1 and if you upgrade vCenter Server 5.1 to vCenter Server 5.5, you must restart the vCenter Infrastructure Navigator virtual appliance.
- Some user interface elements, such as the inventory table or the Navigator portlet on the Summary tab, might take few minutes to populate the data, depending on the number of related services running in your environment.
- After the upgrade of vCenter Infrastructure Navigator from version 2.0 to version 5.8.2, the An internal error has occurred - index 0 specified is out of bounds error message appears in the vSphere Web Client.
Workaround: Clear the cache of the browser and log in again in the vSphere Web Client.
- Discovery fails on virtual machines with a BusyBox Linux installation. with the error Could not find command: netstat. The command is installed on the machine but it does not have all the parameters that vCenter Infrastructure Navigator uses while netstat is running.