Support Support Downloads Knowledge Base Apex Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos] Checklist to troubleshoot telemetry data not received by collector

0

0

Article ID: KB34031 KB Last Updated: 05 Apr 2019Version: 1.0
Summary:

This article provides a checklist to troubleshoot telemetry data not received by the collector.

Symptoms:

Telemetry data not received by collector.

Solution:

Summary of Steps:

  1. Make sure the configuration for the sensor, export-profile and collector servers are complete and correct.
  2. Check if the collector is reachable from the local-address defined under the export-profile.
  3. In the FPC shell, check if the ingress/egress statistics are incrementing or not.
  4. Make sure path-MTU from router to collector is bigger than the payload size of telemetry data.
  5. Verify packets are being transmitted on egress port of router destined for the remote collector.
  6. Confirm there are no firewall filter settings on the collector and output interface of router..
Step Details:

1. Make sure the configuration for the sensor, export-profile, and collector servers are complete and correct.   

Refer to Configuring a Junos Telemetry Interface Sensor (CLI Procedure).

2. Check if the collector is reachable from the local-address defined under the export-profile.

If ping is allowed by the local router output filter and the remote collector server, then try to initiate the ping request from the local router to the collector. Remember to specify the source address as the local-address defined under the export profile:

   -> ping source <local-address> <IP-address-of-collector>
     For instance, in this case, the local-address is 1.1.1.1 and the collector is 2.2.2.2:
   -> ping source 1.1.1.1 2.2.2.2

3. In the FPC shell, check if the ingress/egress statistics are incrementing or not.

3.1 Get the sensor ID:

user@host> show agent sensors
Sensor Information :
    Name                                    : SENSOR_02
    Resource                                : /junos/system/linecard/interface/logical/usage/
    Version                                 : 1.0
    Sensor-id                               : 47721225
    Reporting-interval                      : 60
    Subscription-ID                         : 141254080
 
    Server Information : 
        Name                                : server
        Scope-id                            : 0
        Remote-Address                      : 2.2.2.2
        Remote-port                         : 50000
        Transport-protocol                  : UDP

    Profile Information : 
        Name                                : TELEMETRY_PROFILE
        Address                             : 1.1.1.1
        Port                                : 50001
        Timestamp                           : 1
        Format                              : GPB
        DSCP                                : 255
        Forwarding-class                    : 255

3.2 Get the ingress/egress statistics:

FPC0(host vty)# show agent sensors id 47721225
ID: 47721225 Type: 1 Name: (SENSOR_02)
Sensor Data: 981(953) bytes
Jvision Header: system: host:1.1.1.1 slot: 0, time: Mar  1 19:55:43.272, sequence_number: 12185, sensor_name: SENSOR_02, version: 1.0
=====================================================
Interface = et-0/0/1.0 (896) Parent = ae1.0
Init time: Oct 19 19:59:32 2018

Ingress Statistics
------------------
Packets: 14771725690891   <-- Check if this counter is incrementing.
Bytes: 19888185508695205
Multicast Packets: 0

Egress Statistics
-----------------
Packets: 1298407
227613   <-- Check if this counter is incrementing.
Bytes: 361733758036663

Operational Status
------------------
Status: up


Note: You also can use the shell command below to filter the info, starting a Junos shell from operational mode:
start shell
cprod -A <fpc#> -c "show agent sensors id 47721225" | grep -A 5 "Statistics|Accounting"
 

4. Make sure the path MTU from the router to collector is larger than the payload size of the telemetry data.

The payload size is defined in the export-profile (Junos Telemetry Interface).
 
payload-size bytes (Optional) —Specify the maximum size of exported packets. 

Note: The payload-size option is supported only on the following sensors:
  • /junos/system/linecard/interface/
  • /junos/system/linecard/interface/logical/usage/
  • /junos/system/linecard/firewall/

Default: 5000 bytes.
Range: 2000 through 9192 bytes.

You can find the payload-size for the export profile using one of these two methods:

  • Under operational mode:

       > show agent sensors | find "Profile Information :"

  • Under FPC shell mode:

       start shell pfe network fpc#
       show agent sensors id <sendsor_id> export

     

5. Verify packets are being transmitted on egress port of router destined for the remote collector.

Create a filter is to verify if telemetry packets are being generated and leaving the router to the remote collector.
Example filter:
re0# show firewall family inet filter telemetry-out               
term 1 {
    from {
        source-address {
            1.1.1.1/32;
        }
        destination-address {
            2.2.2.2/32;
        }
        port 50000;       >>>>remote-port
    }
    then {
        count telemetry-out;
        accept;
    }
}
term 2 {
    then accept;
}

 

6. Confirm there are no firewall filter settings (that could be blocking the packets) on the collector and output interface of router.

 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search