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

The following errors are possible:

Onboard Administrator (OA) Connection Errors

Unable to Connect to OA

Error Message: Unable to establish a valid connection to the target system. Unable to connect to any OA hosts.

Description: Ensure the correct OA hostname(s)/IP address(es) were entered when adding your adapter instance.

Unable to Collect from OA

Error Message: Unable to establish a valid connection to the target system. Unable to collect from any OA hosts.

Description: In this scenario, an OA CLI session has been established and a host has been connected to, but data cannot be collected. Ensure the specified host is for the intended OA system.

Unable to Establish Session with Onboard Administrator

Error Message: Unable to establish session with Onboard Administrator.

Description: Confirm you can use the OA CLI to directly establish a session with the OA host.

Unable to Collect Enclosure Name

Error Message: Unable to collect the enclosure name. Ensure host provided is an OA system: {HOSTNAME}

Description: In this scenario, an OA CLI session has been established and a host has been connected to, but data cannot be collected. Ensure the specified host is for the intended OA system.

Invalid Algorithm Parameter Exception

ErrorMessage: Unable to establish a valid connection to the target system.

Description: See this article by our support team to resolve this error.

VCM Connection Errors

Missing VCM User Name

Error Message: VCM password is provided, but VCM user name is not.

Description:Add your VCM user name to the OA and VCM credential.

Missing VCM Password

Error Message: VCM user name is provided, but VCM password is not.

Description:Add the password associated with your VCM user name to the OA and VCM credential.

Unable to Connect to VCM Host

Error Message: Unable to connect to any VCM hosts.

Description:Ensure the VCM credentials entered are correct for the intended VCM host.

Unable to Collect from VCM

Error Message: Unable to collect from any VCM hosts

Description: In this scenario, a VCM CLI session has been established, but the OA is returning a VCM host that is unreachable.

Invalid Algorithm Parameter Exception

ErrorMessage: Unable to establish a valid connection to the target system.

Description: See this article by our support team to resolve this error.

iLO Connection Errors

Unable to Connect to iLO

Error Message: Unable to establish a valid connection to the target system. Unable to connect to the specified iLO host.

Description: Ensure the correct iLO hostname(s)/IP address(es) were entered when adding your adapter instance.

Invalid Port

Error Message: Unable to establish a valid connection to the target system. Invalid port.

Description: Ensure the correct iLO port is specified. Default value is 443.

Invalid Timeout Setting

Error Message: Unable to establish a valid connection to the target system. Invalid timeout.

Description: Ensure the value specified for the Timeout is a positive integer value

Invalid Algorithm Parameter Exception

ErrorMessage: Unable to establish a valid connection to the target system.

Description: See this article by our support team to resolve this error.

Invalid User Name / Password (Authentication Failure)

Error Message: Unable to establish a valid connection to the target system. Invalid iLO user name or password

Description: Ensure the specified iLO user name and password are correct.

Note: The iLO provides a security feature that disables logins after a number of failed attempts. This feature does not need to be changed in order for the Management Pack to work, but the lockout does also apply to connections made by the Management Pack. As a result, a streak of consecutive failed connection tests could cause the iLO to refuse future connections for a period of time. To check if this security feature is causing Test Connection to fail, open the iLO login page. If logins are disabled, there will be a message to alert you. The settings for delay time and number of failed login attempts needed to cause a delay can be adjusted in the iLO settings ( Administration > Access Settings).

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/HPComputeAdapter/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 > Support > 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.