Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Routers to Send JTI Telemetry Data and RPM Statistics to the Data Collectors


Junos Telemetry Interface (JTI) sensors generate data from the PFE (LSP traffic data, logical and physical interface traffic data), and will only send probes through the data-plane. So, in addition to connecting the RE to the management network, a data port must be connected to the collector on one of your devices. The rest of the devices in the network can use that interface to reach the collector.

To configure the routers, use the following procedure:

  1. Configure the devices for telemetry data. On each device, the following configuration is required. The device needs to be set to enhanced-ip mode, which might require a full reboot.

    In this configuration, the remote address is the IP address of the collector (reachable though a data port). The local address should be the loopback, or router-id, which ever is configured on the device profile to identify the device.

  2. Configure RPM probes to measure the interface delays. The following example shows the configuration of probes out of interface ge-0/1/1.0 to the remote address This remote address should be the IP address of the node at the other end of the link.
  3. RPM probes do not yet generate telemetry data, but you can use the rpm-log.slax script to push the results. The script is located in /opt/northstar/data/logstash/utils/junoscripts. Install the script to /var/db/scripts/event on the router. Enable the script by adding it to the event/scripts configuration:

    Probes must be named after the interface being measured.

    The text of the rpm-log.slax script follows. Note that the first part is a comment section providing instructions and examples.