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 routing engine 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.

Note:

You must use Junos OS Release 15.1F6 or later for NorthStar analytics.

To configure the routers, use the following procedure:

  1. Configure the devices (both devices running Junos OS and Junos OS Evolved) for sending telemetry data to the Controller. On each device, the following configuration is required. The device needs to be set to enhanced-ip mode, which might require a full reboot.
    Note:

    • You must configure Junos OS devices that have MPC10 or higher linecards to send telemetry data. Junos OS devices that have line cards older than MPC10 do not need the configuration for sending telemetry data.

      Devices running newer releases of EVO and Junos OS devices with MPC10+ line cards need not be configured to send telemetry data.

    • For NorthStar to correctly process the JTI telemetry packets from MPC10 line cards on routers running Junos OS, ensure that you:

      • Configure remote-port in [services analytics streaming-server server] as 3000

      • Add set services analytics export-profile profile-name payload-size 1400

    • If you are configuring for NorthStar integration with Paragon Insights (formerly HealthBot), use default remote-port 4000 and set the remote-address to the Paragon Insights server IP address.

    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, whichever is configured on the device profile to identify the device.

  2. NorthStar supports bandwidth sizing and container LSPs for SR-TE LSPs. Junos OS release 19.2R1 or later is required for this functionality. There is additional configuration required on the router to enable collection of segment routing data. For example:
  3. Real-time performance monitoring (RPM) enables you to monitor network performance in real time and to assess and analyze network efficiency. To achieve this, RPM exchanges a set of probes with other IP hosts in the network for monitoring and network tracking purposes.

    Configure RPM probes to measure the interface delays. The following examples show the configuration of probes out of interface ge-0/1/1.0 to the remote address 10.101.105.2 (on devices running Junos OS) and et-0/0/3:0.0 to the remote address 10.10.10.1 (on devices running Junos OS Evolved). This remote address should be the IP address of the node at the other end of the link.

    Note:

    The test name must match the interface being measured (test ge-0/1/1.0 and test et-0/0/3:0.0, in the following examples).

    • The following is a sample to configure RPM probes in a device running Junos OS.

    • The following is a sample to configure RPM probes in a device running Junos OS Evolved.

  4. Configure the syslog host using the following commands for both devices running Junos OS and Junos OS Evolved. :
    Note:

    IMPORTANT: To prevent the population of duplicate delay data to the PCS, do not perform this step if you are configuring for integration with Paragon Insights.

  5. RPM probes do not yet generate telemetry data, but you can use the rpm-log.slax script (for devices running Junos OS) or evo-rpm-log.slax (for devices running Junos OS Evolved) 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.

    Use a text editor such as vi to make one addition to the rpm-log.slax script as follows (the bundled script will be updated in a future release):

    Enable the script by adding it to the event/scripts configuration:

    Note:

    IMPORTANT: To prevent the population of duplicate delay data to the PCS, do not perform this step if you are configuring for integration with Paragon Insights.

    • To enable the rpm-log.slax script:

    • To enable the evo-rpm-log.slax script:

      Add the following lines to the evo-rpm-log.slax script to trigger the script to ping the device every sixty seconds:

    The text of the rpm-log.slax script is as follows. Comments are enclosed in /* */.

    The text of the evo-rpm-log.slax script is as follows. Comments are enclosed in /* */.

Related Documentation