Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Junos Telemetry Interface

  • Enhanced support for FIB telemetry streaming (MX240, MX960, MX2020, PTX5000, and PTX1000)—Junos OS Release 22.4R1 introduces enhanced support for forwarding information base (FIB) telemetry streaming based on the OpenConfig Abstract Forwarding Table (AFT) model. We now support the following sensor paths:

    • /network-instances/network-instance/afts/ipv4-unicast/ipv4-entry/state/origin-protocol

    • /network-instances/network-instance/afts/ipv6-unicast/ipv6-entry/state/origin-protocol

    • /network-instances/network-instance/afts/next-hops/next-hop/state/encapsulate-header

    [See Telemetry Sensor Explorer.]

  • Event-driven streaming of sensor data for MPLS LSP record route objects (ACX5448, ACX7100, MX204, MX240, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, PTX1000, and vMX)—Junos OS Release 22.4R1 introduces ON_CHANGE notification for streaming MPLS label-switched path (LSP) record route object statistics. Using ON_CHANGE mode, data values are not streamed but sent only when data values change. Support includes leaf nodes under the resource path /network-instances/network-instance/mpls/signaling-protocols/rsvp-te/sessions/session/record-route-objects/record-route-object/state/.

    [See Telemetry Sensor Explorer.]

  • OpenConfig OSPF configuration and operational state sensors (ACX5448, ACX7100, MX150, MX204, MX240, MX480, MX960, MX10003, MX10008, MX10016, MX2008, MX2010, MX2020, and PTX1000)—Junos OS Release 22.4R1 introduces support for the OpenConfig OSPF data model openconfig-ospfv2.yang (v.0.3.1). We now support configuration and streaming of operational state data under the resource path /network-instances/network-instance/protocols/protocol/ospfv2/.

    To learn about OpenConfig configuration mappings, see Mapping OpenConfig OSPF Commands to Junos Configuration. For state sensors, see Telemetry Sensor Explorer.

  • System health reporting sensors support on gRPC (ACX5448 and ACX710 routers; MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10008, and MX10016 routers; and PTX10002 routers)—Starting in Junos OS Release 22.4R1, Junos telemetry interface (JTI) Junos telemetry interface (JTI) supports data model openconfig-system.yang using gRPC remote procedure calls (gRPC) and provides new health-monitoring sensors.

    [See Telemetry Sensor Explorer.]

  • Telemetry sensor support (MX10004)—Starting in Junos OS Release 22.4R1, Junos telemetry interface (JTI) supports sensors in the following telemetry statistics areas:

    • Transceiver diagnostics

    • Native optics

    • Native fabric statistics

    • Physical Ethernet interface

    • Chassis management error (cmerror) configuration and counters

    • Platform, interface, and alarms

    • Flexible PIC Concentrator (FPC) environment

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

  • Support for gRPC tunnel sessions (MX204, MX240, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, PTX-5000, PTX1000, PTX10002, VMX, and QFX5110)—Starting with Junos OS Release 22.4R1, you can configure a gRPC tunnel session to establish a connection between an external TCP client and a TCP server. The gRPC tunnel session establishes a reverse connection when a TCP client can't reach the TCP server.

    To establish a gRPC tunnel session, include the grpc-tunnel configuration statement in the [edit system services] hierarchy.

    [See gRPC Tunnels Overview.]