Once you have finished Installing the Management Pack (VMAX) and Configuring the Management Pack (VMAX), 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 (VMAX), 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 username or password
Error Message: “Username or password is incorrect.”
Description: Ensure the Unisphere for VMAX username and password are correct.
Trust Store path is invalid
Error Message: “Trust store [$optional_user_specified_path] is invalid: No trusted certificate found.”
Description: Ensure you have added the VMAX host server’s SSL certificate to the vROps Truststore (refer to Adding an SSL Certificate to the vROps Truststore (VMAX)) and have copied the correct path into the Trust Store configuration window.
Network is unreachable
Error Message: “Network is unreachable, or connection timed out. Ensure host and port are correct.”
Description: Ensure the hostname or IP address of your VMAX system is correct. Only IPv4 is supported.
Unable to find enable SSL protocol
Error Message: “Unable to successfully find an enabled SSL protocol to use. We attempted to use the following: [$list_of_ssl_protocols_we_attempted_to_use].”
Description: Determine the SSL protocol enabled on the specified host system, then enable that protocol on the vROps system from which the instance is run.
Checking credentials against a GET request to endpoint
Error Message: “Checking credentials against a GET request to endpoint [performance/Array/keys]”
“GET request to endpoint [performance/Array/keys] unsuccessful”
“GET request to endpoint [performance/Array/keys] unsuccessful: $some_message”
Description: The endpoint returned an empty response. Verify that the Unisphere system is up and responding.
Checking credentials against a POST request to endpoint
Error Message: “Checking credentials against a POST request to endpoint [performance/Array/metrics]”
“POST request to endpoint [performance/Array/metrics] unsuccessful”
“POST request to endpoint [performance/Array/metrics] unsuccessful: $some_message”
Description: The message string could be any of the first four error messages. Refer to their suggested actions.
Symmetrix ID is not valid
Error Message: “If entries were supplied to the optional “Symmetrix ID Whitelist” configuration field, “Checking that provided Symmetrix IDs are valid.” If one of the Symmetrix IDs was invalid, “Symmetrix ID [$id] is not a valid ID to collect against.”
Description: Ensure the Symmetrix IDs entered into the configuration window are correct.
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/EMCVMAXAdapter/ folder.
- Collector log files are located in the $VCOPS_BASE/user/log/ folder.
To set the base log level for the collector in vROps:
- Navigate to Administration > Logs.
- Expand the MASTER folder, then select the COLLECTOR folder.
- Click the Edit Properties icon.
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.