Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Junos Telemetry Interface

  • Number of configurable BMP monitoring stations increases to a maximum of eight (MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10004, MX10008, and vMX)—Starting in Junos OS Release 23.1R1, Junos telemery interface (JTI) delivers initial sync and ON_CHANGE BGP routing information base (also known as routing table) statistics by using remote procedure calls (gRPC) or the gRPC network management interface (gNMI) from a device to an outside collector for a maximum of eight BMP monitoring stations.

  • Network slicing telemetry support for slice queue statistics (MX480, MX960, MX10003, and MX2020)—Starting in Junos OS Release 23.1R1, Junos telemetry interface (JTI) supports slice queue statistics on network slices (logical networks). Network slicing enables network operators to define logical networks on a physical network. A slice comprises a set of nodes, links, and prefixes of a transport network.

    Subscribe to the native sensor /junos/system/linecard/cos/interface/slice/out-queue/ to export egress queue statistics.

    [See Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface) for sensor information. See Hierarchical Class of Service for Network Slicing for network slicing information.]

  • Support for OpenConfig QoS fabric priority classifiers and state sensor (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—Starting in Junos OS Release 23.1R1, we support OpenConfig QoS fabric priority classifiers for IPv6 and MPLS. Support includes configuration and streaming of operational state data.

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

  • OpenConfig QoS schedulers and rewrite support and state sensor support (MX150 (MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016 and vMX)—Starting in Junos OS Release 23.1R1, we support OpenConfig QoS for forwarding classes, classifiers and rewrites, classifiers and rewrite bindings, schedulers, drop profiles, and scheduler maps. Support includes sensor configuration and streaming of operational state data.

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

  • Segment routing telemetry for OSPFv2 (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and VMX)—Starting in Junos OS Release 23.1R1, we support collection and streaming of telemetry data for segment routing with the OSPFv2 protocol. You can record statistics for the Source Packet Routing in Networking (SPRING) traffic per interface, per link aggregation group, and per segment identifier. Support includes OpenConfig and native Junos sensors. To enable collection and export of SR statistics, include the sensor-based-stats statement at the [edit protocol ospf source-packet-routing] hierarchy level.

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

  • Support for vtnet0|1 interface statistics (MX2010 and MX2020 with MPC9E and MPC11E line cards in a Junos node-slicing environment)—Starting in Junos OS Release 23.1R1, Junos telemetry interface (JTI) supports interface sensors for the vtnet0|1 interfaces. A vtnet0 interface communicates between Routing Engines and Packet Forwarding Engines. A vtnet1 interface communicates between the primary and secondary Routing Engines. An MX Series router supports vtnet0|1 interface statistics in either of these scenarios:

    • The router operates as the base system (BSYS).

    • You assign line cards to the router, enabling it to operate as a guest network function (GNF).

    [See Telemetry Sensor Explorer.]