Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Chassis management error (cmerror) sensor support (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 22.4R1 introduces support for the latest version of the OpenConfig data model openconfig-platform-pipeline-counters.yang (v.0.2.1). The upgrade includes updates to leaves under the state sensor path /components/component/intergrated-circuit/pipeline-counters/errors/.

    [See Telemetry Sensor Explorer.]

  • Enhanced support for FIB telemetry streaming (PTX10008)—Junos OS Evolved Release 22.4 introduces enhanced support for forwarding information base (FIB) telemetry streaming based on the OpenConfig Abstract Forwarding Table (AFT) model. Support includes 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 (ACX7100-32C, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 22.4R1 introduces ON_CHANGE notification for streaming MPLS label-switched path (LSP) record route object statistics. ON_CHANGE mode sends updates for sensor data 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.]

  • Fabric block sensors pipeline counters (PTX10004, PTX10008, and PTX10016)——Starting in Junos OS Evolved Release 22.4R1, Junos telemetry interface (JTI) supports data model openconfig-platform-pipeline-counters.yang, which specifies a set of statistics and error counters for each subsystem of a data forwarding ASIC [IC]. This feature covers fabric-block sensors for packet, drop and error categories.

    [See Telemetry Sensor Explorer.]

  • OpenConfig OSPF configuration and operational state sensors (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10008, and PTX10016)—Junos OS Evolved Release 22.4R1 introduces support for OpenConfig OSPF data model openconfig-ospfv2.yang (version 0.3.1). Support includes configuration and streaming of operational state data under resource path /network-instances/network-instance/protocols/protocol/ospfv2/.

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

  • OpenConfig support for node ID and P4RT implicit filtering (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.4R1, Junos telemetry interface (JTI) supports sensors that export telemetry data associated with each Packet Forwarding Engine ASIC instance within a router's line card, such as fpc slot:npu instance.. The NPU mentioned is the same as the Packet Forwarding Engine ASIC chip. Telemetry data includes its type (INTEGRATED_CIRCUIT) and parent FPC slot, all corresponding interface port numbers as fpc slot:npu instance:port number, and the node-id as an identifier for the specific fpc slot:npu instance.

    This feature also supports a CLI configuration to set the node-id. The node-id parameter is an identifier for each PFE ASIC instance across all internal and external routers. Additionally, this feature supports P4Runtime (P4RT) implicit filtering. OpenConfig module openconfig-p4rt defines a set parameters for configuration and state, providing extensions that control P4RT service. You can also use these parameters with other OpenConfig data models.

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

  • Sensor support for firewall filters (PTX10001-36MR, PTX10003, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.4R1, Junos telemetry interface (JTI) supports streaming OpenConfig firewall filter sensors under the data models openconfig-acl.yang (OC-ACL) and openconfig-network-instances policy-forwarding.yang (OC-NI-PF).

    [See Telemetry Sensor Explorer.]

  • System health reporting sensors over gRPC (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016 routers and QFX5130-32CD and QFX5220 switches)—Starting in Junos OS Evolved Release 22.4R1, 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.]

  • System health sensors (PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 22.4R1, Junos telemetry interface (JTI) introduces new system health sensors that stream system health statistics for the chassis or for a hardware component. When subscribing to a system health resource path, the chassis or component's "health" is returned, such as the status, last unhealthy event, and the unhealthy count.

    [See Telemetry Sensor Explorer.]

  • Support for gRPC tunnel sessions (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5220)—Starting with Junos OS Evolved Release 22.4R1, you can configure a gRPC remote procedure call (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.]

  • Telemetry for IPv4/IPv6 traffic statistics (QFX5220)—Junos OS Evolved Release 22.4R1 introduces support for streaming IPv4 and IPv6 transit statistics using resource path /junos/system/linecard/interface/traffic. The following fields will be exported:

    • if_in_ipv4pkts

    • if_out_ipv4pkts

    • if_in_ipv6pkts

    • if_out_ipv6pkts

    To enable IPv6 transit statistics for the physical port, you must configure IPv6 route accounting.

    Support for OpenConfig is available under resource path /interfaces/interface/.

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