Once you have finished Installing the Management Pack (Pure Storage) and Configuring the Management Pack (Pure Storage), 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

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

The following errors are possible:

Bad Host: Unable to get API version. Bad Request: GET https://google.com:443/api/api_version

Error Message: Bad Host: Unable to get API version. Bad Request: GET https://google.com:443/api/api_version.

Action: When attempting to connect to Pure Storage, the Management Pack was unable to find the specified host. Ensure that the host configured when Creating an Adapter Instance (Pure Storage) is available.

Unknown Host: Unable to get API version. Unknown host. Check that host is correct.

Error Message: Unknown Host: Unable to get API version. Unknown host. Check that host is correct.

Action: When attempting to connect to Pure Storage, the Management Pack was unable to find the specified host. Ensure that the host configured when Creating an Adapter Instance (Pure Storage) is correct.

Bad User: Unable to retrieve authentication token from the Pure Storage API. Invalid credentials.

Error Message: Bad User: Unable to retrieve authentication token from the Pure Storage API. Invalid credentials.

Action: When attempting to connect to Pure Storage, the Management Pack was unable to authenticate using the provided user. Ensure the user entered when Creating a Credential (Pure Storage) is correct and has sufficient permissions as indicated in Assigning Pure Storage FlashArray User Privileges (Pure Storage).

Bad Password: Unable to retrieve authentication token from the Pure Storage API. Invalid credentials.

Error Message: Bad Password: Unable to retrieve authentication token from the Pure Storage API. Invalid credentials.

Action: When attempting to connect to Pure Storage, the Management Pack was unable to authenticate using the provided password. Ensure the password entered when Creating a Credential (Pure Storage) is correct.

Bad Port: Unable to get API version. Connection refused: <array FQDN>/<IP>. Check that host is correct, and required port(s) are open.

Error Message: Bad Port: Unable to get API version. Connection refused: <array FQDN>/<IP>. Check that host is correct, and required port(s) are open.

Action: When Creating an Adapter Instance (Pure Storage), ensure that the port configured matches that of your Pure Storage FlashArray's open port.

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/PureStorageFlashArrayAdapter/ 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 Propertiesconfigure_iconicon.

  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.

      Important:

      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.