Description

JUNOS supports ​Telemetry Interface Sensor in default/primary instance only. The interfaces cannot be used in other routing-instances as a source when enabling ​Telemetry Interface Sensor.

Symptoms

When source/destination addresses are in routing-instance (in this case, it’s VRF), there were NO packets out seen when monitoring the interface.

Solution

This is expected behavior.

To enable ​Telemetry Interface Sensor on JUNOS, use the interfaces in the default/primary instance.

Refer to the test results below:

Suppose interface xe-0/1/2 is in VRF, no packets out:

  MX1 (VRF) xe-0/1/2-----------xe-0/1/2 MX2 (pretending to be the server)

When xe-0/1/2 is put back to primary instance, packets out:

  MX1 xe-0/1/2-----------xe-0/1/2 MX2 (pretending to be the server)

Example configurations:

user@host# show services                                    
analytics {
    streaming-server telemetry-server {
        remote-address x.x.x.x;
        remote-port 33333;
    }
    export-profile export-params {
        local-address y.y.y.y;
        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/;
    }
}

Example Results:

When source/destination addresses are in the primary instance, you can see packets out as below:

  <MX1>
user@host# 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
< snip >
2 packets received by filter
0 packets dropped by kernel

When source/destination addresses are in routing-instance (in this case, it’s VRF), there are NO packets out seen:

  <MX2>
user@host# 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

Related Information