Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Collect ON_CHANGE BGP RIB telemetry statistics (MX960, MX2008, MX2010, MX2020, PTX1000, PTX5000, and the PTX10000 line of devices)—Starting in Junos OS Release 22.1R1, Junos telemery interface (JTI) delivers ON_CHANGE BGP routing information base (also known as routing table) statistics using Juniper proprietary remote procedure calls (gRPC) and network management interface (gNMI) from a device to an outside collector.

    To collect statistics, include one of these resource paths in a subscription:

    • /bgp-rib/afi-safis/afi-safi/ipv4-unicast/loc-rib/
    • /bgp-rib/afi-safis/afi-safi/ipv4-unicast/neighbors/neighbor/
    • /bgp-rib/afi-safis/afi-safi/ipv6-unicast/loc-rib/
    • /bgp-rib/afi-safis/afi-safi/ipv6-unicast/neighbors/neighbor/

    [See Telemetry Sensor Explorer.]

  • Consolidated (atomic) statistics delivery for next-hop groups and conditional next-hop groups in JTI (MX960, MX2000, MX10008, MX10016, PTX1000, PTX5000, PTX10002, PTX10008, and PTX10016)—Starting in Junos OS Release 22.1R1, JTI supports consolidated (atomic) data. JTI delivers statistics for next-hop groups and conditional next-hop groups in a single atomic protocol data unit (PDU) instead of across multiple PDUs.

    [See Telemetry Sensor Explorer and gRPC Services for Junos Telemetry Interface.]

  • MACsec statistics (MX104, MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, PTX1000, PTX5000, PTX10001-36MR, PTX10002, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Release 22.1R1, JTI provides ON_CHANGE and periodic streaming of Media Access Control Security (MACsec) statistics using Juniper proprietary gRPC and gNMI from a device to an outside collector. This feature supports the data model openconfig-macsec.yang and augments additional leaves that are outside its scope Additional leaves outside the scope of the data model are augmented.

    To stream MACsec statistics, include the /macsec/ resource path in a subscription.

    [See Telemetry Sensor Explorer.]

  • Collect telemetry statistics for routes programmed through JET API (ACX710, ACX5448, MX150, MX204, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, PTX1000, and PTX10002)—Starting in Junos OS Release 22.1R1, you can collect telemetry statistics for forwarded routing packets programmed by means of Juniper Extension Toolkit (JET) APIs and JTI. GRE tunneling and packet translation between IPv6 and IPv4, introduced in Junos OS Release 21.2R1, supports the routing statistics collected by this feature.

    [See JET APIs on Juniper EngNet and Telemetry Sensor Explorer .]

  • Packet Forwarding Engine discard statistics (PTX1000, PTX5000, and QFX10002-60C)—Starting in Junos OS Release 22.1R1, you can use JTI to stream Packet Forwarding Engine error and drop statistics using UDP (native) or Juniper proprietary gRPC to an outside collector using the resource path /junos/system/linecard/packet/usage/. Use these statistics to optimize traffic engineering and improve your network design. Statistics subscribed to using the resource path are delivered in the following format:

    /components/component[name='FPC0:NPU3']/properties/property[name='hwds-dlu-not-routable']/state/value/

    [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

  • Wireless CUPS telemetry support with JTI (MX240, MX480, and MX960)—Starting in Junos OS Release 21.2R1, you can use JTI to export telemetry statistics for control and user plane separation (CUPS) to proactively manage the mobile-edge user plane agent. You can stream statistics to a collector unless they are event-driven. Event-driven statistics are delivered through ON-CHANGE, not streaming. On the collector side, you can suppress unchanged statistics.

    [See Telemetry Sensor Explorer.]