Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry

  • Support to monitor soft-GRE tunnels and sessions (MX240, MX480, and MX960)—Use Junos telemetry sensors to monitor soft-GRE tunnel or session information. Juniper's YANG modules for native GRE sensors are available at Juniper's telemetry GitHub repository. To configure data collection from the sensors, use the Junos CLI to provision sensors for collecting specific data. Subscribe to the sensor information you want to collect; data is streamed over gRPC or UDP connections. Use the protocol buffer's files to decode the streamed data on the collector. You can retrieve the following soft-GRE sensor information:

    • At the system level, you can obtain the total count of GRE static or dynamic tunnels. You can also obtain information on session types (static, PPPoE, DHCP, and VLAN).
    • At the tunnel level, you can retrieve detailed information about interface name, address types, local or remote addresses, routing instance, and session counts.
    • You can retrieve informatiom about traffic data for inbound and outbound packets, bytes, and rates (packets or bits per second) for each tunnel.

    This data helps monitor and manage the performance of GRE tunnels and their associated sessions.

    The following resource paths are supported:

    • /state/services/soft-gre/counters/static-tunnels
    • /state/services/soft-gre/counters/dynamic-tunnels
    • /state/services/soft-gre/counters/static-sessions
    • /state/services/soft-gre/counters/pppoe-sessions
    • /state/services/soft-gre/counters/dhcp-sessions
    • /state/services/soft-gre/counters/vlan-sessions
    • /state/services/soft-gre/counters/user-sessions
    • /state/services/soft-gre/logical-interfaces/logical-interface/
    • /state/services/soft-gre/logical-interfaces/logical-interface/name
    • /state/services/soft-gre/logical-interfaces/logical-interface/static-tunnels
    • /state/services/soft-gre/logical-interfaces/logical-interface/dynamic-tunnels
    • /state/services/soft-gre/logical-interfaces/logical-interface/static-sessions
    • /state/services/soft-gre/logical-interfaces/logical-interface/pppoe-sessions
    • /state/services/soft-gre/logical-interfaces/logical-interface/dhcp-sessions
    • /state/services/soft-gre/logical-interfaces/logical-interface/vlan-sessions
    • /state/services/soft-gre/logical-interfaces/logical-interface/user-sessions
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/name
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/local-address
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/ remote-address
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/routing-instance
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/static-sessions
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/pppoe-sessions
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/dhcp-sessions
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/vlan-sessions
    • /state/services/soft-gre/tunnel-interfaces/tunnel-interfaces/user-sessions
    • /state/services/soft-gre/session-interfaces/session-interface/
    • /state/services/soft-gre/session-interfaces/session-interface/name

    For more information, see Sensors and Sensor Paths, Guidelines for Streaming Telemetry Data Over UDP | Junos OS | Juniper Networks, Establish a Dial-out Telemetry Connection | Junos OS | Juniper Networks, Decoding Junos Telemetry Interface Data With UNIX Utilities, and Junos YANG Data Model Explorer.

  • Sensor path support for the table connection disable-metric-propagation leaf (ACX710, MX10008, and MX10016)—By default, the OpenConfig protocol sets the destination protocol metric based on the source protocol metric. Set the disable-metric-propagation leaf to true to stop this behavior. The device then sets the metric to zero or a policy-defined value. Subscribe to the following resource paths to obtain sensor-specific information:

    • /network-instances/network-instance/table-connections/table-connection/config/disable-metric-propagation
    • /network-instances/network-instance/table-connections/table-connection/state/disable-metric-propagation

    For more information, see Junos YANG Data Model Explorer.

  • OpenConfig IS-IS enhancements including graceful restart and maximum ECMP paths (MX204, MX240, MX301, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020)—Configure the missing leaves for graceful restart and maximum ECMP paths to achieve compliance with OpenConfig data models for IS-IS protocols. This step ensures remote management across different vendors without requiring device login, by using specific CLI commands to set configurations that include OpenConfig network instances and graceful restart options.

    For more information, see Junos YANG Data Model Explorer.

  • Stream telemetry data in gNMI-based message format over UDP (MX204, MX240, MX301, MX304, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, QFX5100VC, QFX5110, QFX5110-VC, QFX5110-VCF, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, QFX5120-48YM, QFX5200, and QFX5210)—Junos OS 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.proto file. This mechanism supports only STREAM mode with SAMPLE as subscription mode. 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.

    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.]