Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Health monitor sensors and counters (ACX710, ACX5448, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 23.2R1, we support additional health monitor sensors for the following health parameters:

    • Memory

    • License

    • Clock

    • System state

    • SSH server

    • Telnet server

    • Logging

    • Network Time Protocol (NTP)

    • DNS

    • Authentication, authorization, and accounting (AAA)

    [See Junos YANG Data Model Explorer.]

  • IS-IS configuration using OpenConfig (MX204, MX240, MX304, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, and vMX)—Junos OS Release 23.2R1 introduces support for new configuration paths based on OpenConfig data model openconfig-isis.yang version 1.0.0.

    See Mapping OpenConfig ISIS Commands to Junos Configuration.

  • On-box aggregation support (MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX )—Starting in Junos OS Release 23.2R1, we support onbox aggregation of interface, CoS, MPLS, and aggregated Ethernet counters. Off-box aggregation has limited insight into systemic events, such as line card resets or LAG membership changes. On-box aggregation support aggregates the counters at the source and generates a telemetry stream of aggregated PFE statistics and telemetry data. With this data you can reduce production errors at the collector.

    We support these sensors with on-box aggregation:

    • /junos/system/linecard/interface/traffic/

    • /junos/system/linecard/interface/queue/

    • /junos/system/linecard/interface/logical/usage/

    • /junos/system/linecard/cos/interface/interface-set/output/queue/

    • /junos/services/label-switched-path/usage/

    • /qos/interfaces/interface/output/queues/queue/state/

    • /interfaces/interface/state/counters/

    • /interfaces/interface/subinterfaces/subinterface/state/counters/

    • /interfaces/interface/subinterfaces/subinterface/ipv4/state/counters/

    • /interfaces/interface/subinterfaces/subinterface/ipv6/state/counters/

    • /network-instances/network-instance/mpls/lsps/constrained-path/tunnels/tunnel/state/counters/

    • /junos/system/linecard/interface/queue/

    • /junos/system/linecard/qmon-sw/

    • /qos/interfaces/interface/output/queues/queue/state/

    • /qos/interfaces/interface/input/virtual-output-queues/voq-interface/queues/queue/state/

    See Junos YANG Data Model Explorer for OpenConfig sensors and Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface) for native sensors.

  • Support for OpenConfig multicast data model (ACX5448, ACX710, EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100, EX4100-MP, EX4300-MP, EX4300-VC, EX4400-MP, EX4400, EX4650, EX4650-VC, EX9214, MX204, MX240, MX304, MX150, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, vMX, QFX10002-60C, QFX10008, and QFX10016)—Junos OS Release 23.2R1 introduces support for OpenConfig multicast data models openconfig-pim.yang (version 0.4.2) and openconfig-igmp.yang (version 0.3.0). This feature includes telemetry streaming of operational state data and configuration using OpenConfig.

    See Junos YANG Data Model Explorer for state sensors and Mapping OpenConfig Multicast Commands to Junos Configuration for configuration.

  • QoS telemetry on virtual interfaces (MX204, MX480, MX960, MX10004, MX10008, MX10016, MX2010, and MX2020)—Junos OS Release 23.2R1 extends support for streaming statistics for quality-of-service (QoS) queues to the following virtual interface types: pseudowire, GRE, LT, inline service, and link services intelligent queuing interface (LSQ). You can stream QoS queue statistics using OpenConfig or native Junos operational state sensors.

    [For OpenConfig sensors, see Junos YANG Data Model Explorer. For native Junos sensors, see Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

  • Support for configuring the routing-instance and source address for each gRPC tunnel session (MX204, MX240, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, and VMX)—Starting with Junos OS Release 23.2R1, you can configure the routing instance and the source address for each gRPC remote procedure call (gRPC) tunnel session to dial out a connection to the tunnel server.

    To configure the routing instance, add the routing-instance <routing-instance> option and to configure the source address, add the source-address <ip-address> option in the grpc-tunnel configuration statement.

    If you do not configure a routing instance, the gRPC tunnel uses the default routing instance. If you do not configure the source address, the kernel picks the source address that can reach the tunnel server.

    [See gRPC Tunnels Overview and grpc-tunnel].

  • Support for FEC monitoring sensors and counters (MX204, MX240, MX480, MX960, MX2010, MX10008, and MX2020)—Starting in Junos OS Release 23.2R1, we support forward error correction (FEC) monitoring sensors and counters on Ethernet interfaces. You can stream Ethernet FEC mode and see other FEC counters: codeword size, codeword rate, bit errors, corrected words, and uncorrected words.

    [See Junos YANG Data Model Explorer.]

  • Routing Engine and chassis statistics sensors in GNFs (MX240, MX480, MX960, MX2008, MX2010, and MX2020)—Starting in Junos OS Release 23.2R1, Junos telemetry interface (JTI) expands the sensor support for guest network functions (GNFs) to collect Routing Engine and chassis statistics. JTI already supports CPU sensors and line-card sensors (with some limitations) in GNFs. When the sensors cannot export statistics from a GNF, they export them from the base system (BSYS).

    When node sliced, the MX Series router functions as the BSYS. Node slicing creates additional VMs that function as GNFs. The BSYS owns all the hardware components such as chassis, linecards, and switch fabric. GNFs own and implement logical functions and maintain related states.

    Because of this distribution of ownership of hardware components and functions between BSYS and GNFs, the GNFs do not have access to all the information that is available to a standalone router or the BSYS on a node-sliced router. JTI can export complete statistical information from a node-sliced router only if you subscribe to the BSYS and the GNF with the required sensor path.GNFs do not have access to all information that is available to a standalone router or BSYS on a node-sliced router. In order to export complete statistical information from a node-sliced router using JTI, one has to subscribe to both the BSYS and the GNF with the required sensor path.

    [See Junos YANG Data Model Explorer.]

  • Telemetry streaming for IS-IS protocol based on OpenConfig data model (MX204, MX240, MX304, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, and vMX)—Starting in Junos OS Release 23.2R1, the data model for IS-IS is compliant with OpenConfig. The node type for /network-instances/network-instance/protocols/protocol/ is defined as a list which contains user-configurable keys for the protocol name and identifier.

    [See Junos YANG Data Model Explorer.]

  • Telemetry streaming for static and local aggregate routes based on OpenConfig (MX10008)—Starting in Junos OS Release 23.2R1, the data model for static and local aggregate routes is compliant with OpenConfig. The node type for /network-instances/network-instance/protocols/protocol/ is defined as a list which contains user-configurable keys for the protocol name and identifier.

    [See Junos YANG Data Model Explorer.]

  • Upgrade of OpenConfig BGP models (MX480 and vRR)—Junos OS Release 23.2R1 supports an upgrade for the following OpenConfig BGP models to version 9.1.0:

    • openconfig-bgp-global.yang

    • openconfig-bgp-neighbor.yang

    • openconfig-bgp-peer-group.yang

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

    See Junos YANG Data Model Explorer for state sensors and Mapping OpenConfig BGP Commands to Junos Configuration for configuration.

  • Upgrade of OpenConfig BGP RIB models (ACX5448, ACX710, MX204, MX240, MX150, MX480, MX960, MX10003, MX10004, MX10008, MX10016, MX2008, MX2010, MX2020, vRR)—Junos OS Release 23.2R1 supports operational state sensors based on the latest OpenConfig BGP RIB data models:

    • openconfig-rib-bgp-attributes.yang (version 0.8.1)

    • openconfig-rib-bgp-ext.yang (version 0.6.0)

    • openconfig-rib-bgp-shared-attributes.yang (version 0.8.1)

    • openconfig-rib-bgp-table-attributes.yang (version 0.8.1)

    • openconfig-rib-bgp-tables.yang (version 0.8.1)

    • openconfig-rib-bgp-types.yang (version 0.5.0)

    • openconfig-rib-bgp.yang (version 0.8.1)

    The following model versions are no longer supported:

    • openconfig-rib-bgp-ext.yang (version 0.2.0)

    • openconfig-rib-bgp-types.yang (version 0.2.0)

    • openconfig-rib-bgp.yang (version 0.2.0)

    See Junos YANG Data Model Explorer.