Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Physical Ethernet interface sensor (ACX7509)— Junos telemetry interface (JTI) supports ON_CHANGE and periodic streaming of physical Ethernet interface statistics by using RPC developed by Google (gRPC) or gRPC Network Management Interface (gNMI) from an ACX7509 device to an external collector. This feature supports OpenConfig model openconfig-if-ethernet.yang (physical interface level) version 2.6.2 (no configuration). Use the base sensor path /interfaces/interface/ethernet/state/ in a gRPC or gNMI subscription to export statistics from the ACX7509 device to an external collector.

    With this feature you can now subscribe physical ethernet interface sensors on ACX7509 platform.

    [See Junos YANG Data Model Explorer.]

  • MACsec statistics (ACX7100-32C, ACX7100-48L, ACX733, ACX7348, and ACX7509)—Junos telemetry interface (JTI) provides ON_CHANGE and periodic streaming of Media Access Control Security (MACsec) statistics by using RPC developed by Google (gRPC) or gRPC Network Management Interface (gNMI) from a device to an outside collector. This feature supports the data model openconfig-macsec.yang. Additional leaves outside the scope of the data model are augmented. To stream MACsec statistics, include the sensor path /macsec/ in a subscription.

    [See Junos YANG Data Model Explorer.]

  • Enhanced telemetry with multiple gRPC servers and multi-port gRPC services (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5130-48C, QFX5130-48CM, QFX5130E-32CD, QFX5220, QFX5230-64CD,QFX5700, and QFX5700E)—You can configure multiple RPC developed by Google (gRPC) servers with distinct services, listening addresses, and ports by using the Junos telemetry interface (JTI). This feature enhances control over service management and telemetry data collection. You can also configure TLS certificates for secure communications. For example, you can configure a server to listen on a specific port and serve only designated gRPC services, enhancing flexibility and security in your telemetry setup.

  • Native YANG state model and telemetry support for network stack protocol statistics (ACX Series, QFX Series, and PTX Series)—You can use a native YANG state model and telemetry to monitor network stack protocol statistics on EVO platforms. Telemetry provides real-time data streaming for protocols such as TTP, ICMP, MPLS, TCP, and more. These statistics, previously available through CLI commands, are now accessible through telemetry streaming, ensuring real-time updates. This feature provides a comprehensive and dynamic monitoring solution, configurable in either "on-change" or "periodic" mode, enhancing your network's observability and performance management.

    [See Junos YANG Data Model Explorer.]

  • Telemetry support through gRPC interface for real-time network monitoring (ACX7509)—You can use telemetry to gain real-time insights into network performance and the current state of network elements. This feature supports new OpenConfig sensor paths that provide a high-frequency, asynchronous push model for exporting performance data, focusing on key metrics such as I/O, error counters, and queue statistics. Use the gRPC interface to integrate with client applications and model-driven telemetry to receive data in YANG models.

    [See Junos YANG Data Model Explorer.]

  • MPLS RSVP-TE sensors, OpenConfig for MPLS and LDP, and event-driven streaming (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, and ACX7509)—Junos telemetry interface (JTI) supports MPLS RSVP-TE sensors through the openconfig-mpls-rsvp.yang (version 4.0.0) data model. The feature supports LDP with the openconfig-mpls-ldp.yang data model. The feature also supports openconfig-mpls.yang(version 3.2.2), openconfig-mpls-types.yang (version 3.2.1), openconfig-mpls-te.yang (version 3.2.2), and openconfig-mpls-static.yang (version 3.2.2). The device supports these OpenConfig configurations mpls global, mpls named-explicit-path, and mpls tunnels. It supports the state groups MPLS tunnels, MPLS named-explicit-path, MPLS static label-switched-path, MPLS -TE interface attributes, and MPLS tunnel state counters. Use ON_CHANGE notifications to stream MPLS LSP record route object statistics only when data changes. The resource path /network-instances/network-instance/mpls/signaling-protocols/rsvp-te/sessions/session/record-route-objects/record-route-object/state/ is supported.

    The feature supports the data models:

    • openconfig-mpls-ldp.yang

    • 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 feature supports the OpenConfig configurations:

    • mpls global

    • mpls named-explicit-path

    • mpls tunnels

    The feature supports the state groups:

    • MPLS tunnels

    • MPLS named-explicit-path

    • MPLS -TE interface attributes

    • MPLS static label-switched-path

    • MPLS tunnel state counters

    The feature supports the sensor path /network-instances/network-instance/mpls/signaling-protocols/rsvp-te/sessions/session/record-route-objects/record-route-object/state/.

    Use ON_CHANGE notifications to stream MPLS LSP record route object statistics only when data changes.

    [See Junos YANG Data Model Explorer.]

  • Support for OpenConfig network instance configuration and state ( ACX7024, ACX7024X, ACX7332, and ACX7348)—Use Junos telemetry interface (JTI) to monitor new sensors for network instance statistics in the openconfig-network-instance.yang,openconfig-local-routing.yang, and openconfig-routing-policy.yang modules. OpenConfig network instance commands map to Junos OS configurations. For mapping details, see Mapping OpenConfig Network Instance Commands to Junos Operation | Junos OS | Juniper Networks.

    [See Junos YANG Data Model Explorer.]

  • Support for OSPF, IS-IS, BGP-RIB, ARP, and SR-TE OpenConfig configurations and state data streaming (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X)—Junos telemetry interface (JTI) supports the following features:

    • Support for OpenConfig OSPF data model openconfig-ospfv2.yang(version 0.3.1) includes OpenConfig configuration and streaming of operational state data under resource path /network-instances/network-instance/protocols/protocol/ospfv2/.

    • Support for OpenConfig IS-IS configurations and sensors based on the OpenConfig data model openconfig-isis.yang(version 1.0.0).

    • OpenConfig support for proxy Address Resolution Protocol (ARP) and IPv6 duplicate address detection (DAD) configurations based on the OpenConfig data model openconfig-if-ip.yang (version 3.0.0).

    • JTI support for operational state sensors based on the following latest OpenConfig BGP-RIB data models:

      Table 1: BGP-RIB Data Models
      File Name Version
      openconfig-rib-bgp-attributes.yang 0.8.1
      openconfig-rib-bgp-ext.yang 0.6.0
      openconfig-rib-bgp-shared-attributes.yang 0.8.1
      openconfig-rib-bgp-table-attributes.yang 0.8.1
      openconfig-rib-bgp-tables.yang 0.8.1
      openconfig-rib-bgp-types.yang 0.5.0
      openconfig-rib-bgp.yang 0.8.1

      The following model versions are no longer supported:

      Table 2: Unsupported BGP-RIB Data Models
      File Name Version
      openconfig-rib-bgp-ext.yang 0.2.0
      openconfig-rib-bgp-types.yang 0.2.0
      openconfig-rib-bgp.yang 0.2.0

      The following OpenConfig BGP models are upgraded to version 9.1.0:

      Table 3: Upgraded BGP RIB Data Models
      File Name Version
      openconfig-bgp-global.yang 9.1.0
      openconfig-bgp-neighbor.yang 9.1.0
      openconfig-bgp-peer-group.yang 9.1.0

      The upgraded models introduce new leaves for operational state sensors and OpenConfig configurations.

    • Telemetry streaming of operational state data for segment routing–traffic engineering (SR-TE) policy. State sensors are based on the OpenConfig data model openconfig-srte-policy.yang. You can subscribe to SR-TE sensors using the resource path /network-instances/network-instance/segment-routing/te-policies.

    New sensor paths are added for the above features.

    [See Junos YANG Data Model Explorer.]

  • TWAMP sensor and OpenConfig BFD (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, and ACX7509)— Junos telemetry interface (JTI) supports:

    • Periodic streaming of Two-Way Active Measurement Protocol (TWAMP) statistics for IPv4 and IPv6 traffic in TWAMP-managed and TWAMP Light sessions

      Proprietary RPC developed by Google (gRPC) and gRPC Network Management Interface (gNMI) support the sensor that streams this data.

    • OpenConfig configuration and BFD state data streaming.

      OpenConfig BFD configuration commands map to relevant Junos OS commands. See Mapping OpenConfig BFD Commands to Junos Operation.

    New sensor paths are added for these features.[See Junos YANG Data Model Explorer.]

  • Health monitoring sensors (ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)— Junos telemetry interface (JTI) provides native sensors to monitor device infrastructure health. Device streams health statistics that external collectors use to track performance.

    Use the resource path /state/system/infrastructure/junos-evolved/ to view the health statistics.

    These sensors stream details such as cluster data, distributor statistics, Distributed Data Store (DDS) client information, common resources, and indexes for Identity Management and Device Management .

    [See Junos YANG Data Model Explorer.]

  • Per-segment list telemetry support for colored and uncolored SR-TE tunnels(ACX7100-32C, ACX7100-48L, ACX7332, ACX7024, ACX7024X, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—You can configure per-segment-list sensors for segment routing–traffic engineering (SR-TE) tunnels to generate sensor IDs and collect traffic statistics from both ingress and transit points.The feature generates unique sensor IDs for each segment-list and provides the option to disable specific sensors. Additionally, updated SR-TE displays and route installations reflect per-path sensor information, ensuring comprehensive visibility and management of network telemetry.