Description

This article clarifies that the Junos OS supports ​Telemetry Interface Sensor only in the default/primary instance and that interfaces in other routing-instances cannot be used as source while enabling ​ Telemetry Interface Sensor .

 

Symptoms

Example

When we put xe-0/1/2 in VRF, no packets go out: 

MX1 (VRF) xe-0/1/2-----------xe-0/1/2 MX2 (telemetry server)

When we put xe-0/1/2 back into the primary instance, packets go out as expected. 

MX1 xe-0/1/2-----------xe-0/1/2 MX2 (telemetry server)

The Telemetry Interface Sensor configurations are as shown below: 

user@MX1# show services                                    
analytics {
    streaming-server telemetry-server {
        remote-address 23.1.1.3;
        remote-port 33333;
    }
    export-profile export-params {
        local-address 23.1.1.2;
        local-port 21111;
        dscp 20;
        forwarding-class assured-forwarding;
        loss-priority high;
        reporting-rate 20;
        format gpb;
        transport udp;
    }
    sensor interface-1 {
        server-name telemetry-server;
        export-name export-params;
        resource /junos/system/linecard/interface/logical/usage/;
    }
}

Results

When the source/destination addresses are in the primary instance, packets go out: 

user@MX1# run monitor traffic interface xe-0/1/2
verbose output suppressed, use <detail> or <extensive> for full protocol decode
Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
Address resolution timeout is 4s.
Listening on xe-0/1/2, capture size 96 bytes
 
14:42:04.361824  In IP a23-1-1-3.deploy.static.akamaitechnologies.com > a23-1-1-2.deploy.static.akamaitechnologies.com: ICMP a23-1-1-3.deploy.static.akamaitechnologies.com udp port 33333 unreachable, length 36
14:42:24.486997  In IP a23-1-1-3.deploy.static.akamaitechnologies.com > a23-1-1-2.deploy.static.akamaitechnologies.com: ICMP a23-1-1-3.deploy.static.akamaitechnologies.com udp port 33333 unreachable, length 36
^C
2 packets received by filter
0 packets dropped by kernel

When source/destination addresses are in the routing-instance (in this case, it is VRF), no packets are seen to go out: 

user@MX2# run monitor traffic interface xe-0/1/2
verbose output suppressed, use <detail> or <extensive> for full protocol decode
Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
Address resolution timeout is 4s.
Listening on xe-0/1/2, capture size 96 bytes
 
^C
0 packets received by filter
0 packets dropped by kernel

 

Solution

It is recommended that you use interfaces in the default or primary instance if you want to enable ​Telemetry Interface Sensor on the Junos OS because this feature is not supported in a routing-instance.

 

Related Information