Junos Telemetry Interface

date_range 15-Aug-24

arrow_backward

arrow_forward

OpenConfig configuration and sensor support for ZR and ZR+ optical transceivers (MX2020)—Junos OS Release 24.2R1 supports the OpenConfig configuration and data streaming of ZR and ZR+ optics. You can create a a subscription in INITIAL_SYNC or TARGET_DEFINED mode using Juniper proprietary Remote Procedure Call (gRPC) service or gRPC Network Management Interface (gNMI). Use the OpenConfig command /components/component/transceiver/config/fec-mode for configuration. Use these resource paths in a subscription to stream data:
- /components/component/transceiver/state/
- /components/component/transceiver/physical-channels/
- /components/component/optical-channel/state/
This feature is based on data models openconfig-terminal-device.yang (version 1.8.0), openconfig-platform-transceiver.yang (version 0.8.0), and openconfig-transport-types.yang (version 0.14.0).
[For the optics configuration, see Mapping OpenConfig Interface Commands to Junos Configuration. For sensors, see Junos YANG Data Model Explorer.]
OpenConfig MAC address and MAC address and IP path sensor support (ACX710, ACX5448, ACX5448-M, ACX5448-D, EX2300, EX2300-MP, EX2300-C, EX2300-VC, EX3400, EX3400-VC, EX4100-24MP, EX4100-48P, EX4100-48T, EX4100-24P, EX4100-48MP, EX4100-24T, EX4100-F-48P, EX4100-F-24P, EX4100-F-24T, EX4100-F-12P, EX4100-F-48T, EX4100-F-12T, EX4300-MP, EX4300VC, EX4400-24MP, EX4400-24P, EX4400-24MP, EX4400-24P, EX4400-24T, EX4400-24X, EX4400-48F, EX4400-48MP, EX4400-48P, EX4400-48T, EX4650, EX4650-48Y-VC, MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX, QFX10002-60C, QFX5100VC, QFX5110, QFX5110-VC, QFX5110-VCF, QFX5120-32C, QFX5120-48T, QFX5120-48T-VC, QFX5120-48Y, QFX5120-48Y-VC, QFX5120-48YM, QFX5200, QFX5210, QFX5500, QFX10002, QFX10008, and QFX10016)—Junos OS Release 24.2R1 supports the streaming of telemetry MAC address and MAC address and IP path data from the forwarding database to a collector using the OpenConfig resource path /network-instances/network-instance/fdb/. This feature is based on data models openconfig-network-instance.yang (version 1.2.0) and openconfig-network-instance-l2.yang (version 1.2.0).
[See Junos YANG Data Model Explorer.]
Support for QoS classifier, rewrite, and scheduler OpenConfig configurations and state sensor support (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX)—Junos OS Release 24.2R1 supports the QoS classifier, rewrite and scheduler OpenConfig configurations and state sensors using Junos telemetry interface (JTI). This feature includes support for term ID, behavior aggregate (BA) classifiers for IPv4 and IPv6, and Differentiated Services Code Point (DSCP). The feature also supports term ID for rewrites and the sequence ID and burst size for scheduler maps. We support these OpenConfig configurations:
- /qos/classifiers/classifier/terms/term/config
- /qos/classifiers/classifier/terms/term/config/id
- /qos/classifiers/classifier/terms/term/conditions/ipv4/config/dscp-set
- /qos/classifiers/classifier/terms/term/conditions/ipv6/config/dscp-set
- /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/config/sequence
- /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/two-rate-three-color/config/be
We support these state sensors:
- /qos/classifiers/classifier/terms/term/state
- /qos/classifiers/classifier/terms/term/state/id
- /qos/classifiers/classifier/terms/term/conditions/ipv4/state/dscp-set
- /qos/classifiers/classifier/terms/term/conditions/ipv46state/dscp-set
- /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/state/sequence
- /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/two-rate-three-color/state/be
[For QoS OpenConfig configurations, see Mapping OpenConfig QoS Commands to Junos Configuration. For sensors, see Junos YANG Data Model Explorer.]
IP oc-aft supports periodic streaming of selected prefixes (MX2020)—Junos OS Release 24.2R1 supports periodic streaming of specific prefixes under the IP OpenConfig Abstract Forwarding Table (oc-aft) sensor child path /network-instances/network-instance/afts/. To enable prefix filtering on the target (source) device, include the prefix statement at the [edit fib-streaming prefix-list table table-name family family-name] hierarchy level. When you enable this feature, only interfaces with the required prefixes and their corresponding next-hop and next-hop group containers are exported to the oc-aft collector. Reducing the set of interfaces to only the ones of interest to the collector decreases the overall CPU and resource usage on Routing Engines, Flexible PIC Concentrators (FPCs), and Modular Port Concentrators (MPCs). The recommended periodic interval for streaming resource paths under /network-instances/network-instance/afts/ is 5 minutes.
[See Configuring Prefix Filtering, prefix-list, show fib-streaming state, and Junos YANG Data Model Explorer.]
OpenConfig compliance and support for SR-TE sensors (MX240, MX304, MX480, MX960, MX2010, MX2020 MX10003, MX10004, MX10008, and MX10016)—Junos OS Release 24.2R1 supports OpenConfig-compliant Segment Routing–Traffic Engineering (SR-TE) sensors. This feature includes per segment list data for colored tunnels and new resource paths for existing colored sensors. You can stream data from a device to a collector using native (UDP) sensors, Juniper proprietary Remote Procedure Call (gRPC) service, or gRPC Network Management Interface (gNMI).
[For sensors, see Junos YANG Data Model Explorer.]
Platform telemetry sensor support (MX10004 and MX10008)—Junos OS Release 24.2R1 supports platform sensors that stream telemetry using Juniper proprietary Remote Procedure Call (gRPC) service or gRPC Network Management Interface (gNMI). ON_CHANGE, INITIAL_SYNC, and TARGET_DEFINED subscription modes as well as zero-suppression are supported. The following sensors are supported for all power entry modules (PEMs) and fans:
- /components/component/properties/property
- /components/component/state/temperature
- /components/component/state
- /components/component/fan/state
- /components/component/power-supply/state
[See Understanding OpenConfig and gRPC on Junos Telemetry Interface. For sensors, see Junos YANG Data Model Explorer.]
Queueing block pipeline sensor support (MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—Junos OS Release 24.2R1 supports queueing block pipeline sensors. Stream data about Packet Forwarding Engine counters at a granular level using Junos telemetry interface (JTI) with native (UDP), Juniper proprietary Remote Procedure Call (gRPC) service, or gRPC Network Management Interface (gNMI). Use these sensors in a subscription to export data:
- /components/component/integrated-circuit/pipeline-counters/packet/queueing-block/
- /components/component/integrated-circuit/pipeline-counters/drop/queueing-block/
[For sensors, see Junos YANG Data Model Explorer.]
QoS OpenConfig and operational state sensor support (MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX)—Junos OS Release 24.2R1 supports QoS configurations and sensors you can use to manage the Junos CoS features drop profile and traffic control profile, as well as stream state data for these features. The OpenConfig data model openconfig-qos (version 0.9.1) supports these enhancements.
[For OpenConfig configuration, see Mapping OpenConfig QoS Commands to Junos Configuration. For sensors, see Junos YANG Data Model Explorer.]
Native inline flow monitoring for IPFIX sensor support (MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, and vMX)—Junos OS Release 24.2R1 supports native streaming of inline flow monitoring for IP Flow Information Export (IPFIX) operational states. To stream data, use the sensor /state/sampling/flow-monitoring.
[For sensors, see Junos YANG Data Model Explorer.]
Additional sensor support for oc-aft streaming of FIB telemetry (MX240, MX960, and MX2020)—Junos OS Release 24.2R1 extends OpenConfig Abstract Forwarding Table (oc-aft)-based streaming of forwarding information base (FIB) telemetry to support specific leaves under IPv4-unicast, IPv6-unicast, next-hop-groups, and next-hops containers. The support is based on the OpenConfig data model openconfig-aft.
You must meet the existing requirements to stream telemetry data and also include the oc-tlv statement at the [edit routing-options forwarding-table] hierarchy level to enable statistics collection.

[See forwarding-table and show fib-streaming. For sensors, see Junos YANG Data Model Explorer.]
OpenConfig configuration and state sensor support for AFI-SAFI policies (MX960, MX10003, MX10004, MX10008, and MX10016)—Junos OS Release 24.2R1 supports export and import policies under address family indicator (AFI) and subsequent address family identifier (SAFI). OpenConfig support is for IPv4 and IPv6 unicast address families. Junos CLI-configured policies have priority over policies configured with OpenConfig. For example, if you configure a policy using OpenConfig and another policy using Junos OS CLI under the same neighbor, the latter policy takes effect. We support these OpenConfig configurations:
- /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/config/import-policy
- /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/config/export-policy
We support these state sensors:
- /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/state/import-policy
- /network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/afi-safis/afi-safi<IPV4/V6_UNICAST>/apply-policy/state/export-policy
[For configurations, see Mapping OpenConfig BGP Commands to Junos Configuration. For sensors, see Junos YANG Data Model Explorer.]
View number of programmable routes for VRF instances and VNIs (MX304 and MX10003)—Starting in Junos OS Release 24.2R1, you can view the number of programmable routes per virtual routing and forwarding (VRF) instance and virtual network identifier (VNI) using either the Junos OS CLI or using a sensor, stream the data to a collector. To view the number of routes with the CLI, use the show programmable-rpd clients route-summary display-vni-data command. To stream the VNI count to a collector using telemetry, include the sensor state/routing-instances/routing-instance/routing-tables/routing-table/summaries/programmed/clients/client/protocols/protocol/vnis/vni[id='id'] in a subscription.

Use this feature to improve the performance and efficiency of your device. It is more efficient to check the number of routes with telemetry and CLI than to use gRPC API calls.

[For the CLI command, see show programmable-rpd clients route-summary. For sensors, see Junos YANG Data Model Explorer.]
OpenConfig configuration and state sensor support for default leaves for IS-IS (MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, and MX10016)—Junos OS Release 24.2R1 supports OpenConfig configuration and state sensor support for default leaf values, closing endpoint gaps for the IS-IS protocol. This feature is based on the OpenConfig data model openconfig-isis.yang version (version 1.0.0).
[See Mapping OpenConfig IS-IS Commands to Junos Configuration and Junos YANG Data Model Explorer.]

arrow_backward PREVIOUS Junos OS API and Scripting

NEXT arrow_forward MPLS

Release Notes: Junos OS Release 24.2R1

Junos Telemetry Interface

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry