Once you have finished Installing the Management Pack (Nutanix) and Configuring the Management Pack (Nutanix), check the Collection State and Collection Status for the adapter instance on the Solutions page. If they show as Not Collecting or No Data Receiving, respectively, the following troubleshooting topics can help you diagnose and correct common problems with your adapter instance.

  • Test Connection Errors
  • Adapter and Collector Log Files

Test Connection Errors

When Creating an Adapter Instance (Nutanix), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.

The following errors are possible:

Incorrect Host

Error: “Unable to establish a valid connection to the target system. Incorrect host.”

Action: Ensure the hostname or IP address specified for your endpoint when Creating an Adapter Instance (Nutanix) is correct.

Unauthorized Login

Error: “Unable to establish a valid connection to the target system. Unauthorized Login.”

Action: Ensure your Nutanix username and password specified when Creating a Credential (Nutanix) are correct.

GET request to endpoint [/v1/containers] unsuccessful

Error: “Unable to establish a valid connection to the target system. GET request to endpoint [/v1/containers] unsuccessful.”

Action: Because no response was returned from the target system, ping the host to eliminate any network-related issues.

Adapter and Collector Log Files

You can review adapter errors in the adapter and collector log files, which can be viewed in the vROps UI or in an external log viewer.

  • Adapter log files are located in the $VCOPS_BASE/user/log/adapters/NutanixAdapter/ folder.
  • Collector log files are located in the $VCOPS_BASE/user/log/ folder.

To set the base log level for the collector in vROps:

  1. Navigate to Administration > Logs.
  2. Expand the MASTER folder, then select the COLLECTOR folder.
  3. Click the Edit Properties configure_icon icon.
  4. In the Root logger level drop-down menu, select the desired option.
  • The default logging level is warning.
  • To troubleshoot issues, set the logging level to info.
  • To view detailed messages, including micro steps, queries, and returned results, set the logging level to debug.
Note: If you set the logging level to debug, log files can become large very quickly. Set the logging level to debug only for short periods of time.

For more information about viewing log files and modifying levels, refer to the vROps online help.