Junos Telemetry
-
Support for LSP traffic sensors (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, ACX7024X)—Junos telemetry supports sensors to monitor LSP-RSVP and LDP-LSP traffic statistics. The following sensor paths are added to retrieve traffic information:
Native sensor paths:
/junos/services/label-switched-path/usage/
/junos/services/ldp/label-switched-path/ingress/usage/
/junos/services/ldp/label-switched-path/transit/usage/
Openconfig sensor path:
/network-instances/network-instance/mpls/lsps/constrained-path/tunnels/tunnel/Note:- Zero-value counters are not exported.
-
Telemetry is not supported for Point-to-Multipoint (P2MP) and dynamically configured LSPs.
Use the
'show agent sensors'command to view all active sensors.For more information, see Junos YANG Data Model Explorer.
-
Stream telemetry data in gNMI-based message format over UDP (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, ACX7024X, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, PTX12008, QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5700, QFX5700E, QFX5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—Junos OS Evolved uses a dial-out mechanism to send telemetry data to a collector over UDP . The message format is defined in the
jnx_gnmi_over_udp.protofile. OnlySTREAMmode withSAMPLEas subscription mode is supported. The message contains full key name and value pair information so the collector does not require data models for processing or consuming the telemetry data.[See Streaming Telemetry Data Over UDP, Establish a Dial-out Telemetry Connection, streaming-server (Junos Telemetry Interface), export-profile (Junos Telemetry Interface), show services analytics dialout statistics, and Junos YANG Data Model Explorer.]