Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • 400G-ZR and ZR+ optics sensor support (PTX10003 and PTX10008)—Starting in Junos Evolved OS Release 22.3R1, Junos telemetry interface (JTI) supports optical channel state and performance monitoring sensors. The sensors stream statistics using Juniper proprietary remote procedure calls (gRPC) and gRPC Network Management Interface (gNMI). We also support both INITIAL_SYNC and target-defined subscriptions for these sensors.

    [See Telemetry Sensor Explorer.]

  • BGP policy sensor upgrade (ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Release 22.3R1, JTI supports data model openconfig-bgp-policy.yang version 6.0.2 (upgraded from version 4.0.1). New BGP policy sensors are supported.

    [See Telemetry Sensor Explorer.]

  • DDoS native sensor support (PTX10008 and PTX10016)—Starting in Junos OS Evolved Release 22.3R1, Junos telemetry interface (JTI) supports native distributed denial of service (DDoS) sensors to monitor DDoS violations. When a violation occurs, DDoS telemetry data is streamed to monitoring stations.

    See Telemetry Sensor Explorer.]

  • Telemetry support for firewall resource utilization (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016)—Junos OS Evolved Release 22.3R1 introduces telemetry support for firewall resource utilization statistics using the OpenConfig sensor /components/component/integrated-circuit/pipeline-counters. The sensor displays the total supported filter entries and the used entries in terms of count and bytes.

    [See Firewall Resource Utilization.]

  • Initial sync enhancement for FIBstreaming (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved 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 (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.3R1, Junos telemetry interface (JTI) supports the sensor /network-instances/network-instance/afts/next-hops/next-hop/state/lsp-name.

    [See Telemetry Sensor Explorer.]

  • MPLS RSVP-TE sensor support (ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos Evolved OS Release 22.3R1, Junos telemetry interface (JTI) supports the data model openconfig-mpls-rsvp.yang version 4.0.0. It also supports the new RSVP-Traffic Engineering (RSVP-TE) sensors.

    [See Telemetry Sensor Explorer.]

  • MPLS OpenConfig configuration and sensor support (ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.3R1, Junos telemetry interface (JTI) supports these 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

    The release supports these OpenConfig configurations:

    • MPLS global

    • MPLS named-explicit-path

    • MPLS tunnels

    The release supports these 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.]

  • Packet Forwarding Engine sensors for device monitoring, discard counters, and forwarding table occupancy in JTI (PTX10003)—Junos OS Evolved Release 22.3R1 supports streaming Packet Forwarding Engine statistics to an external collector. You can subscribe to sensors for device monitoring, discard counters, and forwarding table occupancy by using the following resource paths:

    • /interfaces/

    • /junos/system/linecard/packet/usage/

    • /junos/system/linecard/npu/memory/

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

  • Platform sensor support for components, optics, physical interfaces, and Ethernet interfaces (ACX7100-32C, and ACX7100-48L, and ACX7024)—Starting in Junos OS Evolved Release 22.3R1, Junos telemetry interface (JTI) supports sensors for components, optics, physical interfaces, and Ethernet interfaces.

    For optics sensors, see Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface). For other sensors, see Telemetry Sensor Explorer.]

  • Support for FTI sensors (PTX10003)—Junos OS Evolved Release 22.3R1 introduces telemetry support for flexible tunnel interface (FTI) sensors. You can subscribe to collect FTI statistics by using either OpenConfig or native Junos resource paths.

    For OpenConfig sensor support, see Telemetry Sensor Explorer. For native Junos support, see Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).

  • Telemetry support for CoS page drop reporting (PTX10003)—Starting in Junos OS Evolved Release 22.3R1, you can collect statistics on packet drops caused by page timeouts by subscribing to the resource path /junos/system/linecard/page-drops/page-drop/. Page drop statistics include page drop counter, interface information, and queue details.

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

  • Telemetry support for CoS ingress packet drop accounting (QFX5220)—Junos OS Evolved Release 22.3R1 introduces telemetry support to account for packets that are dropped because of ingress port congestion. Counters for priority flow control (PFC), explicit congestion notification (ECN), and ingress drops are exported using the sensor /junos/system/linecard/interface/traffic. Counters for PFC, ECN, and ingress drops are also exported using OpenConfig sensor /interfaces/interface/. Priority group (PG) buffer utilization is exported using the sensor /junos/system/linecard/qmon-sw/.

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

  • Telemetry support for DDoS sensors (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 22.3R1 introduces telemetry support for distributed denial-of-service (DDoS) sensors. You can stream DDoS statistics from a device to a collector by including the resource path /junos/system/linecard/ddos/ in a subscription.

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

  • VLAN sensor support (PTX10001-36MR, PTX10003, PTX10004, and PTX10008)—Starting in Junos OS Evolved Release 22.3R1, Junos telemetry interface (JTI) supports the data model openconfig-vlan.yang version 3.2.1, including VLAN sensor support.

    [See Telemetry Sensor Explorer.]