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

The following errors are possible:

Could Not Create NX-API Client

Error Message: Could not create NxApiClient.

Description: Check the following:

  • Ensure the NX-API username and/or password are correct.
  • Ensure port is correct. 

    Note: Default ports are 443 for NX-API (HTTPS) and 80 for NX-API (HTTP)
  • Check NX-API status on port [port]. Use CLI command show nxapi on the switch to see configured NX-API ports.
  • Ensure the host is reachable.

No Switch Found in SNMP IP Range

Error Message: No switch found in SNMP IP range.

Description: Check the following:

  • Ensure the switch is on and configured to use SNMP v2c or v3.
  • Ensure the vROps server IP has permission to access SNMP.
  • Ensure the community string or other SNMP credentials are correct.
  • Ensure the management port IP is in the IP range.

SNMP IP Range Incorrectly Formatted

Error Message: SNMP IP range formatted incorrectly.

Description: If you entered an SNMP IP range when Creating an Adapter Instance (Cisco Networking), ensure the SNMP IP range was formatted correctly. The recommended maximum range is 254 IP addresses (a /24 or /120 in CIDR notation). Larger ranges are not supported. Example correct formats in CIDR notation are: 10.6.14.0/24. (IPv4) and 2620:0:2d0:200:1f00:400::7/120 (IPv6). Can also be individual IP or comma-separated list of IPs.

Connection refused to [host]. Check Port.

Error Message: Connection refused to [host]. Check Port.

Description: Ensure the correct port was entered when Creating an Adapter Instance (Cisco Networking). The default ports are: 161 for SNMP, 80for NX-API (HTTP), and 443 for NX-API (HTTPS).

Note: If entering vCenter credentials to create relationships to the ESXi host, the following vCenter-related Test Connection errors are also possible:

SSL Error During Attempt to Collect from vCenter

Error Message: Encountered SSL error when trying to collect from vCenter [vSphere Host].

Description: Ensure SSL is enabled on your vCenter host.

vCenter Hostname Not Found

Error Message: vCenter hostname [vSphere Host] not found.

Description: Ensure the correct vSphere host was entered when Creating a Credential (Cisco Networking) and is reachable.

Unable to Log In to vCenter Host

Error Message: Unable to log into vCenter host [vSphere Host] with user [vSphere User Name].

Description: Ensure the correct vCenter User Name and Password were entered.

vCenter Host is an invalid URL

Error Message: vCenter host [vSphere Host] is an invalid URL.

Description: Ensure the vCenter hostname entered when Creating a Credential (Cisco Networking) is a valid URL (e.g., FQDN, IPv4/IPv6 address).

Error Occurred While Attempting to Connect to vCenter Host

Error Message: Error occurred while attempting to connect to vCenter host [vSphere Host].

Description: Ensure the correct vSphere host entered when Creating a Credential (Cisco Networking) and is reachable.

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/CiscoNetworkingAdapter/ 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_icon icon.
  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.