Once you have finished Installing the Management Pack (F5 BIG-IP) and Configuring the Management Pack (F5 BIG-IP), 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 (F5 BIG-IP), click Test Connection after entering all of your configuration settings to ensure vROps can connect to the specified host.

The following errors are possible:

Unable to Authenticate

Error Message: “Unable to Authenticate with User Name and Password.”

Description: Ensure the correct F5 BIG-IP User Name and Password was entered

Unable to Reach Host and Port

Error Message: “Unable to Reach Host and Port."

Description: Ensure the correct port number and F5 BIG-IP Management IP or DNS name was entered for your F5 BIG-IP System.

Not Enough Permissions

Error Message: “User Credentials Do Not Have Enough Permissions.”

Description: You must have a minimum of an Auditor user role with iControl REST API access assigned to your F5 BIG-IP credentials.

"Virtual" Is Selected as License Type

Error Message: “Detected a Physical Device, but Virtual Is Selected as License Type.”

Description: Ensure the correct license type is selected in the Manage Solution window when configuring your adapter instance.

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/BigIpAdapter/ 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_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.
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.