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] Telemetry Interface Sensor is not supported in routing-instance

0

0

Article ID: KB35633 KB Last Updated: 28 Oct 2020Version: 1.0
Summary:

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.

Cause:
This is expected behavior.
Solution:

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 Links

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