close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Introduction
- play_arrow Overview
- play_arrow Access the Paragon Automation GUI
- play_arrow Access the Paragon Planner
  - Access Paragon Planner Desktop Application
- play_arrow Configure SMTP, LDAP, and Portal Settings
- play_arrow Manage Users
- play_arrow Manage Roles
- play_arrow Manage User Groups
- play_arrow Identity Providers
play_arrow Workflows
- play_arrow Base Platform
  - Onboard and Manage Devices
- play_arrow Paragon Pathfinder
- play_arrow Paragon Planner
- play_arrow Paragon Insights
play_arrow Manage Devices and Network
- play_arrow Devices
- play_arrow Device Groups
- play_arrow Device Images
- play_arrow Network
- play_arrow Network Groups
- play_arrow Topology Filter
play_arrow Manage Device Templates and Configuration Templates
- play_arrow Configuration Templates
- play_arrow Device Templates
play_arrow Manage Playbook, Rules, and Resources
play_arrow Manage Sensor Settings, Insights Settings, and Data Summarization Profiles
play_arrow Configure Your Network
play_arrow Monitoring
- play_arrow Monitor Network Health
  - About the Network Health Page
  - Activate Time Inspector View
- play_arrow Manage Alarms and Alerts
- play_arrow Monitor Jobs
- play_arrow Analytics
play_arrow Reports
- play_arrow Health Reports
- play_arrow Network Reports
  - Network Reports Overview
  - View Network Reports
- play_arrow Maintenance Reports
  - Maintenance Reports Overview
  - View Maintenance Reports
- play_arrow Inventory Reports
  - Inventory Reports Overview
  - View Inventory Reports
- play_arrow Demand Reports
  - Demand Reports Overview
  - View Demand Reports
play_arrow Administration
- play_arrow Manage E-mail Templates
- play_arrow Manage Audit Logs
- play_arrow Configure External EMS
- play_arrow Manage Task Scheduler
- play_arrow Manage Security Settings
  - About the Security Settings Page
  - Configure Security Profiles for SSL Authentication
- play_arrow License Management

list Table of Contents

English

keyboard_arrow_right

Configure Routers to Send JTI Telemetry Data and RPM Statistics to the Data Collector

Release: Paragon Automation 24.1

date_range 14-Jul-23

arrow_backward

arrow_forward

Junos Telemetry Interface (JTI) sensors generate data (LSP traffic data, logical and physical interface traffic data) from the Packet Forwarding Engine (PFE), 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 the analytics feature.

To configure the routers, use the following procedure:

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.

Note:

Use default remote-port 4000 and set the remote-address to the Paragon Insights virtual IP address.

content_copy zoom_out_map
set chassis network-services enhanced-ip
set services analytics streaming-server ns remote-address 192.168.10.100
set services analytics streaming-server ns remote-port 4000
set services analytics export-profile ns local-address 10.0.0.10
set services analytics export-profile ns reporting-rate 2
set services analytics export-profile ns format gpb
set services analytics export-profile ns transport udp
set services analytics sensor ifd server-name ns
set services analytics sensor ifd export-name ns
set services analytics sensor ifd resource /junos/system/linecard/interface/
set services analytics sensor ifl server-name ns
set services analytics sensor ifl export-name ns
set services analytics sensor ifl resource /junos/system/linecard/interface/logical/usage/
set services analytics sensor lsp server-name ns
set services analytics sensor lsp export-name ns
set services analytics sensor lsp resource /junos/services/label-switched-path/usage/
set services analytics sensor sr-te-color server-name ns
set services analytics sensor sr-te-color export-name ns
set services analytics sensor sr-te-color resource /junos/services/segment-routing/traffic-engineering/ingress/usage/
set services analytics sensor sid server-name ns
set services analytics sensor sid export-name ns
set services analytics sensor sid resource /junos/services/segment-routing/sid/usage/
set services analytics sensor sr-te-tunnels server-name ns
set services analytics sensor sr-te-tunnels export-name ns
set services analytics sensor sr-te-tunnels resource /junos/services/segment-routing/traffic-engineering/tunnel/ingress/usage/
set protocols mpls sensor-based-stats
set protocols source-packet-routing telemetry statistics

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.

Bandwidth sizing and container LSPs are supported 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:

content_copy zoom_out_map
set groups jvision services analytics sensor sr-te-tunnels server-name ns
set groups jvision services analytics sensor sr-te-tunnels export-name ns
set groups jvision services analytics sensor sr-te-tunnels resource /junos/services/segment-routing/traffic-engineering/tunnel/ingress/usage/

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.

You must 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 10.101.105.2. 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, in this example).

content_copy zoom_out_map
set services rpm probe northstar-ifl test ge-0/1/1.0 target address 10.101.105.2
set services rpm probe northstar-ifl test ge-0/1/1.0 probe-count 11
set services rpm probe northstar-ifl test ge-0/1/1.0 probe-interval 5
set services rpm probe northstar-ifl test ge-0/1/1.0 test-interval 60
set services rpm probe northstar-ifl test ge-0/1/1.0 source-address 10.101.105.1
set services rpm probe northstar-ifl test ge-0/1/1.0 moving-average-size 12
set services rpm probe northstar-ifl test ge-0/1/1.0 traps test-completion
set services rpm probe northstar-ifl test ge-0/1/1.0 hardware-timestamp
set services rpm probe northstar-ifl test ge-0/1/1.0 probe-type icmp-ping-timestamp

arrow_backward PREVIOUS View Job Status

NEXT arrow_forward Configure Routers to Advertise Link Statistics through BGP-LS

Paragon Automation User Guide

Configure Routers to Send JTI Telemetry Data and RPM Statistics to the Data Collector

Stay in touch

Helped me install or use the product
Accelerated my deployment

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

Paragon Automation User Guide

Configure Routers to Send JTI Telemetry Data and RPM Statistics to the Data Collector

Related Documentation

Stay in touch