Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Support for AGF sensors (MX204, MX240, MX480, MX960, and MX10003)—Starting in Junos OS Release 22.3R1, you can use Access Gateway Function (AGF)-specific sensors in Junos telemetry interface (JTI) to collect data on AGF interactions. Use the data to gain early detection to problems occurring in real time, optimize traffic engineering, and improve the design of your network.

    [See Telemetry Sensor Explorer.]

  • BGP policy sensor upgrade (ACX710, ACX5448, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, PTX1000, PTX5000, PTX10002, and vRR)—Starting in Junos OS Release 22.3R1, Junos telemetry interface (JTI) supports data model openconfig-bgp-policy.yang version 6.0.2 (upgraded from version 4.0.1). JTI also supports new BGP policy sensors.

    [See Telemetry Sensor Explorer.]

  • Packet Forwarding Engine DDoS sensor support with JTI (MX960, MX10004, MX10008 and MX2020 operating with Module Port Concentrator (MPC) 10 or 11 or the LC9600 Line Card)—Starting in Junos OS Release 22.3R1, JTI supports distributed denial-of-service (DDoS) telemetry sensors. To stream DDoS statistics from a device to a collector, include the resource path /junos/system/linecard/ddos/) in a subscription. You can stream statistics using UDP (native) or Juniper proprietary gRPC and gNMI. This feature supports the Openconfig data model junos/ui/openconfig/yang/junos-ddos.yang.

    Currently, there are 227 packet types for DDoS. To maintain a reasonably sized data stream, data is exported for all protocols that have traffic using the zero-suppression model.

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

  • Support for logical interface-set sensors (MX204, MX240, MX480, MX960, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016 with Trio chipset EA, ZT, and YT-based fixed systems and modular systems line cards)—Starting in Junos OS Release 22.3R1, Junos telemeytry interface (JTI) supports logical interface (IFL)-set sensors. The sensors stream queue statistics using Juniper proprietary gRPC and gRPC Network Management Interface (gNMI) or by means of UDP. Zero suppression (suppressing zero values in statistics from streamed data) is also supported.

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

  • Support for MPLS RSVP-TE sensors (ACX710, ACX5448, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, PTX1000, and PTX10002 )—Starting in Junos OS Release 22.3R1, Junos telemetry interface (JTI) supports data model openconfig-mpls-rsvp.yang version 4.0.0. It supports new RSVP-TE sensors.

    [See Telemetry Sensor Explorer.]

  • Support for MPLS OpenConfig configuration and sensors (ACX710, ACX5448, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX10016, PTX1000, and PTX10002 )—Starting in Junos OS Release 22.3R1, Junos telemetry interface (JTI) supports the following data models:

    • openconfig-mpls.yang version 3.2.2

    • openconfig-mpls-types.yang version 3.2.1

    • openconfig-mpls-te.yang version 3.2.2

    • openconfig-mpls-static.yang version 3.2.2

    JTI supports the following OpenConfig configurations:

    • MPLS global

    • MPLS named-explicit-path

    • MPLS tunnels

    JTI supports the following state groups:

    • MPLS tunnels

    • MPLS named-explicit-path

    • MPLS static label-switched-path

    • MPLS-TE interface attributes

    • MPLS tunnel state counters (dependent on the Packet Forwarding Engine)

    [See Telemetry Sensor Explorer and Mapping OpenConfig MPLS Commands to Junos Configuration.]

  • INITIAL_SYNC enhancement for FIB streaming (MX240, MX960, MX2010, MX2020, PTX1000, PTX5000, and PTX10008)—Junos OS Release 22.3R1 introduces improved performance time for the INITIAL_SYNC of telemetry statistics. This enhancement applies to subscription requests for the top-level sensor path /network-instances/network-instance/afts. The INITIAL_SYNC feature gives the collector a complete view of the current state of every field on the device for that sensor path.

    [See Enabling “INITIAL_SYNC” Subscription Mode through gNMI.]

  • Sensor for LSP name of MPLS next hops (MX240, MX960, MX2020, PTX1000, and PTX5000)—Starting in Junos OS Release 22.3R1, Junos telemetry interface (JTI) supports the /network-instances/network-instance/afts/next-hops/next-hop/state/lsp-name sensor. This sensor will stream the LSP name associated with the nexthop.

    [See Telemetry Sensor Explorer.]

  • Support for VLAN sensors (ACX5448, ACX5448-M, ACX5448-D, and ACX710 routers, EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-48MP, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-48T, EX4100-F-24T, EX4100-F-12P, EX4100-F-12T, EX4300-MP, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, EX4650-48Y-VC and EX9208 switches, MX204, MX240, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2010, MX2020, PTX10008, and PTX10016 routers and vMX)—Starting in Junos OS Release 22.3R1, Junos telemetry interface (JTI) supports the data model openconfig-vlan.yang version 3.2.1, including sensor support to stream VLAN and MAC- limit operational states through telemetry.

    [See Telemetry Sensor Explorer.]