Known troubleshooting information can help you diagnose and correct common problems with the vRealize Infrastructure Navigator management pack.

This section provides information for troubleshooting vRealize Infrastructure Navigator error messages and connection problems with vCenter Server.

Troubleshooting vRealize Infrastructure Navigator

Error Message

Troubleshooting

Unable to Connect to vCenter Server

Check the vCenter Server URL.

Check the routing from the collector running the vRealize Infrastructure Navigator management pack to the vCenter Server VM.

Verify that vCenter Server is the supported version.

Unable to log in to vCenter Server

Check the vCenter Server credentials.

Unable to connect to Inventory Service

Check the routing from the collector running the vRealize Infrastructure Navigator management pack in the Inventory Service VM. The URL appears in the error message.

Make sure the Inventory Service is running.

Unable to check vRealize Infrastructure Navigator status

Make sure that the vRealize Infrastructure Navigator is deployed and that discovery is turned ON.

In the Applications dashboard, Applications appear without any VMs.

Possible causes:

The vSphere management pack instance was not defined for the vCenter instance that the vRealize Infrastructure Navigator management pack is connecting to.

The vRealize Infrastructure Navigator management pack instance was defined before the vSphere management pack instance.

Suggested troubleshooting:

Make sure the vSphere management pack instance is defined and collecting for the correct vCenter Server instance.

Restart the collector from the vRealize Operations Manager terminal. /usr/lib/vmware-vcops/collector/bin/CollectorService.sh restart

Remove the vRealize Infrastructure Navigator management pack instance and create a vRealize Infrastructure Navigator management pack instance.