Troubleshooting Connectivity with Sensor Collector

In order to connect Assurance Sensor F100 or F25 devices to Provider Connectivity Assurance, Assurance Sensor F100 or F25 must first connect to Sensor Collector; Sensor Collector then connects to Analytics.

From the perspective of Assurance Sensor F100 or F25’s Telemetry application, the connection status and notice shown from the CLI console can indicate whether the connection to Sensor Collector has been successful.

In any event of failure, syslog event messages will be logged; these messages can be helpful in debugging the handshake communications between Assurance Sensor F100 or F25 and Sensor Collector.

Notes:

• To configure and stream Assurance Sensor F100 or F25 PM data to Sensor Collector, see PM Telemetry.
• To display the connection notice between Assurance Sensor F100 or F25 and Sensor Collector, execute the show telemetry reporter-type command. For more information, see the Telemetry Commands.

To troubleshoot connectivity with Sensor Collector:

1. Begin by reading the Checking if Sensor Collector is Configured Properly article. This article provides the information needed to confirm if Sensor Collector is:

• Connected to Provider Connectivity Assurance
• Configured correctly
• Listening on the correct ports for Assurance Sensor Agent and Assurance Sensor F100 or F25 data.

2. Search for a log such as the following:

15:43:23.351 processIdentificationMessage ▶ INFO 050 DATA_BROKER - Authenticated data connection with agent {agent-id} established

• Where {agent-id} corresponds to the identifier for your Assurance Sensor Agent. This indicates that Assurance Sensor F100 or F25 has successfully connected to Sensor Collector.

At this stage, everything should be up and connected. However, if Assurance Sensor F100 or F25 is reporting that it is unable to connect to Sensor Collector or if the above log is not appearing, checking for error logs on the Sensor Collector side may provide the required insight to determine what went wrong.