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 (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5130-48C, and QFX5220)—Starting in Junos OS Evolved 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.

  • Non-default VRF support for streaming FIB anomalies (PTX10008 and PTX10016)—Starting in Junos OS Evolved Release 23.1R1, Junos telemetry interface (JTI) introduces support for non-default virtual routing and forwarding (VRF) user route Third-Party Attachments (TPAs). TPAs provide more information about an error and are added on top of the errored object. In Junos OS Evolved, the Packet Forwarding Engine (known as a producer) attaches or clears TPAs to the routes during route installation or asynchronously at a later time. The forwarding information base telemetry daemon (FIBTB) (FIB is also known as forwarding table) is an error consumer. The FIBTD listens to and reports anomalies in a native model to the collector. In this way, the system maintains accurate state information.

    The existing FIB anomaly feature supports only default VRF user route TPAs for streaming anomalies. This feature supports non-default VRF user route TPAs.

    Use Juniper proprietary remote procedure call (gRPC) services to stream or export ON_CHANGE FIB statistics to an outside SDN collector using the following sensors:

    /state/system/anomalies/fib/route-tables/route-table[name]/route/inet/inet-entry[prefix]/status

    /state/system/anomalies/fib/route-tables/route-table[name]/route/inet/inet-entry[prefix]/timestamp

    /state/system/anomalies/fib/route-tables/route-table[name]/route/inet6/inet6-entry[prefix]/status

    /state/system/anomalies/fib/route-tables/route-table[name]/route/inet6/inet6-entry[prefix]/timestamp

    [See Error TPAs for Route Installation for information about TPAs. See Telemetry Sensor Explorer for sensor information.]

  • OpenConfig QoS configuration and operational state sensors (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Starting in Junos OS Evolved Release 23.1R1, we introduce support for OpenConfig QoS forwarding classes, classifiers, and rewrites. Support includes configuration and streaming of operational state data.

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

  • Platform sensors for chassis components (ACX7509 and PTX10001-36MR)—Starting in Junos OS Evolved Release 23.1R1, Junos telemetry interface (JTI) supports operational state sensors for chassis backplane, fabric, fan, power supply, and storage components based on the OpenConfig model openconfig-platform.yang. Telemetry data for each component is streamed under the path /components/component[name=component-name]/.

    [See Telemetry Sensor Explorer.]

  • Segment routing telemetry for OSPFv2 (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)—Junos OS Evolved Release 23.1R1 introduces support for the collection and streaming of telemetry data for segment routing (SR) with the OSPFv2 protocol. Statistics are recorded 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.]

  • VOQ buffer utilization monitoring (PTX10003)—Starting in Junos OS Evolved Release 23.1R1, we support the export of buffer utilization data for CoS virtual output queues (VOQs). Using this feature, you can stream telemetry data for peak queue length. Monitoring this data assists in preventing micro-bursts and high buffer utilization for a given queue. To enable VOQ queue-depth monitoring, configure the monitoring-profile statement at the [edit class-of-service] hierarchy level. To export data to a collector, use the following resource paths:

    /junos/system/linecard/qmon-sw/

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

    [See VOQ Queue-depth Monitoring for information about VOQs. See Telemetry Sensor Explorer for sensor information.]