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

The following VNX File errors are possible:

Error: Unable to establish a valid connection to the target system. Cannot connect to Primary Control Station. Check hostname, username, and password.

Action: Ensure the hostname, username, and password for the Primary Control Station are correct.

Error: Unable to establish a valid connection to the target system. Command not found, nas path may be incorrect.

Action: Ensure the nas path is correct.

The following VNX Block errors are possible:

Error: Unable to establish a valid connection to the target system. Connection failed. Returned: Could not connect to the specified host.

Action: Ensure the hostname is correct.

Error: Unable to establish a valid connection to the target system. Connection failed. Returned: Cannot run Program.

Action: Ensure the NaviSecCLI utility is installed and that the appropriate path was entered in the adapter configuration window. To manually verify that your connection information is correct and your system is accessible, run the following command from your command prompt:

  • Windows: C:\Program Files (x86)\EMC\Navisphere CLI\NaviSECCli.exe” -User <User Name> -Password <Password> -Scope 0 -h <hostname or IP address> lun -list -all
  • Linux: /opt/Navisphere/bin/naviseccli -User <User Name> -Password <Password> -Scope 0 -h <hostname or IP address> lun -list -all

Error: Unable to establish a valid connection to the target system. Connection failed. Returned: Invalid scope.

Action: Ensure a 0, 1, or 2 was entered in the adapter configuration window.

Error: Unable to establish a valid connection to the target system. User name, password and/or scope incorrect; User name, password and/or scope incorrect.

Action: Ensure the username and password are valid for the scope specified.

Error: “Library or configuration file for NaviSecCLI is missing or corrupt.”

Action:In order to resolve this issue on Windows vROps boxes, complete the following steps:

Note: If this error occurs in Linux, you will probably have to su admin and run naviseccli security -certificate -cleanup.
  1. Open a command prompt as the SYSTEM user. This can be done in a few ways: Creating a service to open the command prompt interactively (deprecated, but functional as of Microsoft Windows Server 2008 R2)
    • sc create cmdsvc binpath= “cmd /K start” type= own type= interact
    • sc start cmdsvc
    • psexec (http://ss64.com/nt/psexec.html)
    • remote.exe tool as part of the Windows Debugger (remote /c [host] SYSCMD)
  2. Run the following command in the SYSTEM-user command prompt: NaviSECCli.exe security -certificate -cleanup.
  3. Attempt Test Connection again in vROps. If it fails with the following error, try again: “Connection failed. Returned: Error occurred while trying to connect: ‘[host]’. Message : File does not match signature.” After performing these steps, Test Connection should pass.

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/emcvnx<block or file>_adapter3/ 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.
Caution: 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.