RPM and TWAMP statistics sensor support for Junos Telemetry Interface

You can export Two-Way Active Management Protocol (TWAMP) and real-time performance monitoring (RPM) statistics. TWAMP (described in RFC 5357) and RPM are two methods to measure traffic performance between endpoints. These methods work by sending active probe packets and measuring parameters such as packet loss, delay, and jitter between the endpoints. These statistics provide RPM and TWAMP monitoring data results collected by Juniper devices. You can use this information to ensure service level agreements, improve network design, and optimize traffic engineering.

Export TWAMP and RPM statistics through JTI using gRPC streaming. The following resource paths are supported:

• /junos/rpm/probe-results/probe-test-results/
• /junos/rpm/history-results/history-single-test-results/ 
• /junos/rpm/server/active-servers/
• /junos/twamp/client/control-connection/
• /junos/twamp/client/probe-test-results/
• /junos/twamp/client/history-test-result/
• /junos/twamp/server/control-connection/

To provision the sensor to export data through remote procedure call (gRPC) streaming, use the telemetrySubscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module. OpenConfig and Network Agent packages are bundled into the Junos image by default. OpenConfig can be found as a default package named junos-openconfig, and Network Agent content exists in the Junos as a daemon through the na-telemetry package. The OpenConfig package can still be installed as an add-on package on top of the default package if you want to upgrade OpenConfig without upgrading Junos OS.