Junos Telemetry | Junos OS Evolved

Export FIB data to external collectors using Junos telemetry (PTX10008, PTX10002-36QDD)—Use Junos telemetry to stream or export Forwarding Information Base (FIB) statistics to external collectors. Telemetry data is streamed in "ON_CHANGE" mode. This feature supports the OpenConfig YANG model OC-AFT. To enable and manage FIB streaming, use the following CLI commands on the client device:

To enable tracing, use the set system trace application application-name node node-name level level command at the [edit system] hierarchy. For example, set system trace application fibd node re0 level info.
Use set system fib-streaming and delete system fib-streaming statements at the [edit] hierarchy level to launch or terminate the process.
Use the set system fib-streaming traceoptions file file-name statement at the [edit] hierarchy level to configure a logging file.
Use the set system fib-streaming traceoptions flag flag-name statement at the [edit] hierarchy level to configure various trace parameters.
Use the set system fib-streaming traceoptionslevel level-name statement at the [edit] hierarchy level to configure log levels.
Use the restart fib-streaming command to restart the process.

To view FIB streaming information, use the following operational mode commands:

show fib-streaming
show fib-streaming next-hop-groups
show fib-streaming next-hops
show fib-streaming routes ipv4-unicast
show fib-streaming routes ipv6-unicast
show fib-streaming routes mpls

To view the trace data for the specified application use show trace application app-name command. For example, show trace application fibtd.

Navigate to the sensor path /network-instances/network-instance/afts/ on the Junos YANG Data Model Explorerto view all the supported sensors. For information on telemetry modes, see Telemetry Modes. For sensor and sensor path information, see Junos YANG Data Model Explorer.

[See Junos YANG Data Model Explorer, Configuring IP-AFT Prefix Filtering, trace (System), and show trace.]

Sensor path support for the table connection disable-metric-propagation leaf (PTX10001-36MR, PTX10008, PTX10016)—By default, the OpenConfig protocol sets the destination protocol metric based on the source protocol metric. Set the disable-metric-propagation leaf to true to stop this behavior. The device then sets the metric to zero or a policy-defined value. Subscribe to the following resource paths to obtain sensor-specific information:

/network-instances/network-instance/table-connections/table-connection/config/disable-metric-propagation
/network-instances/network-instance/table-connections/table-connection/state/disable-metric-propagation

For more information, see Junos YANG Data Model Explorer.

OpenConfig IS-IS enhancements including graceful restart and maximum ECMP paths (PTX10004, PTX10008, PTX10016)—To achieve compliance with OpenConfig data models for IS-IS protocols, configure the missing leaves for graceful restart and maximum ECMP paths. This step ensures remote management across different vendors without requiring device login, by using specific CLI commands to set configurations that include OpenConfig network instances and graceful restart options.

For more information, see Junos YANG Data Model Explorer.

Export 400G ZR and ZR+ transceiver, terminal device, and optics data to external collectors using Junos telemetry (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Use Junos Telemetry to stream terminal device, transceiver, and optical channel (state and performance) statistics from PTX10001-36MR, PTX10004, PTX10008, and PTX10016 devices to external collectors. This information facilitates enhanced performance management and monitoring. To configure a telemetry subscription to deliver data to your collector, see Telemetry Data Subscriptions over gNMI and Establish a Dial-in Telemetry Connection.

Subscribe to the following resource paths for terminal data, transceiver, and optical channel statistics:

/components/component/optical-channel/config/operational-mode
/components/component/optical-channel/state/operational-mode
/components/component/transceiver/physical-channel/channel/state/output-power/max
/components/component/transceiver/physical-channel/channel/state/output-power/min
/components/component/transceiver/physical-channel/channel/state/output-power/avg
/components/component/transceiver/physical-channel/channel/state/output-power/interval
/components/component/transceiver/physical-channel/channel/state/output-power/max-time
/components/component/transceiver/physical-channel/channel/state/output-power/min-time
/terminal-device/logical-channels/channel/config/loopback-mode
/terminal-device/logical-channels/channel/state/loopback-mode

View the complete list of supported sensors in the Junos YANG Data Model Explorer.

[See Establish a Dial-in Telemetry Connection and Junos YANG Data Model Explorer.]

Stream telemetry data in gNMI-based message format over UDP (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, ACX7024X, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, PTX10016, PTX12008, QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5700, QFX5700E, QFX5220, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)—Junos OS Evolved uses a dial-out mechanism to send telemetry data to a collector over UDP . The message format is defined in the jnx_gnmi_over_udp.proto file. Only STREAM mode with SAMPLE as subscription mode is supported. The message contains full key name and value pair information so the collector does not require data models for processing or consuming the telemetry data.

[See Streaming Telemetry Data Over UDP, Establish a Dial-out Telemetry Connection, streaming-server (Junos Telemetry Interface), export-profile (Junos Telemetry Interface), show services analytics dialout statistics, and Junos YANG Data Model Explorer.]