[j-nsp] Junos Telemetry Interface

[Roger Wiklund]

Hi

Native sensors:
https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/sensor-edit-services-analytics.html

OpenConfig sensors:
https://www.juniper.net/documentation/en_US/junos/topics/reference/general/junos-telemetry-interface-grpc-sensors.html

Plugins to consume JTI for common open sources tools:
https://www.juniper.net/documentation/en_US/junos/topics/concept/jti-opensource-plugins.html

Personally I run OpenConfig with Telegraf + InfluxDB + Grafana.

Telegraf has a built-in input plugin for Juniper Openconfig, so it takes
like 5 minutes to enable.
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/jti_openconfig_telemetry

OpenNTI is good for demo/test but not really suitable for production.

/Roger

On Mon, Apr 13, 2020 at 5:46 AM Aaron Gould <aaron1 at gvtc.com> wrote:

> You’re welcome Colton.  I understand there are 2 different ways to do
> telemetry on Juniper.  One called Native and the other called
> gRPC/openconfig.  I’ve done the Native form.  I think the native form is a
> configured form where by which the network device constantly streams the
> sensor objects… and conversely, the gRPC form is subscription based where
> the management app/computer, subscribes to the network device to receive
> telem data objects.
>
>
>
> I understand the native form to be executed in hardware near the monitored
> object….and because of this, highly scalable.    And the grpc/openconfig
> form runs on re cpu.
>
>
>
> I don’t think we’ve gotten native telemetry to work on ACX.  But I have it
> running on MX960’s.
>
>
>
> I understand the grpc/openconfig method requires you to download some
> code/software to the network device.
>
>
>
> Collector I use is the OpenNTI project.  Grafana (web ui) (or a less known
> Cronograf, which I actually use and like), InfluxDB (TSDB), fluentd, and
> other components.  I must credit Dave, my coworker and resident Linux
> genius in assisting my with the server side collector setup.  Some
> helpful/related links below….
>
>
>
>
>
> https://puck.nether.net/pipermail/juniper-nsp/2018-October/036602.html
>
>
>
>
>
>
> https://openeye.blog/2017/06/26/using-opennti-as-a-collector-for-streaming-telemetry-from-juniper-devices-part-1/
>
>
>
>
>
>
> https://www.juniper.net/documentation/en_US/junos/topics/concept/junos-telemetry-interface-oveview.html
>
> look under “telemetry sensors and data models”
>
>
>
>
>
>
> https://community.grafana.com/t/how-to-send-juniper-router-telemetry-to-grafana/11071/9
>
>
>
>
>
> -Aaron
>
>
>
>
>
> From: Colton Conor [mailto:colton.conor at gmail.com]
> Sent: Saturday, April 11, 2020 9:05 AM
> To: Aaron Gould
> Cc: Juniper List
> Subject: Re: [j-nsp] Junos Telemetry Interface
>
>
>
> Aaron,
>
>
>
> Thanks, this is indeed helpful. What collector are you using to store and
> view this telemetry data? Also, have you had any luck with getting JTI to
> work on your ACX gear? This only JTI feature is see for the ACX line
> according to the feature explorer is:
> https://apps.juniper.net/feature-explorer/feature-info.html?fKey=8978 <
> https://apps.juniper.net/feature-explorer/feature-info.html?fKey=8978&fn=Specify%20Routing%20Instance%20for%20JTI>
> &fn=Specify%20Routing%20Instance%20for%20JTI I am not sure if that means it
> fully supports JTI or not.
>
>
>
>
>
> On Fri, Apr 10, 2020 at 11:53 AM Aaron Gould <aaron1 at gvtc.com> wrote:
>
> Not sure if this is what you are looking for, but here are some of the
> sensor agents that I enabled on my MX routers....
>
> Maybe it's the linecard or interface specific ones that give me the bits in
> bits out utilization graphs.
>
> set services analytics sensor my-sensor-14 server-name my-grafana-srvr
> set services analytics sensor my-sensor-14 export-name my-exprt-prfl
> set services analytics sensor my-sensor-14 resource
> /junos/system/linecard/interface/
> set services analytics sensor my-sensor-1 server-name my-grafana-srvr
> set services analytics sensor my-sensor-1 export-name my-exprt-prfl
> set services analytics sensor my-sensor-1 resource
> /junos/system/linecard/packet/usage/
> set services analytics sensor my-sensor-2 server-name my-grafana-srvr
> set services analytics sensor my-sensor-2 export-name my-exprt-prfl
> set services analytics sensor my-sensor-2 resource
> /junos/system/linecard/cpu/memory/
> set services analytics sensor my-sensor-12 server-name my-grafana-srvr
> set services analytics sensor my-sensor-12 export-name my-exprt-prfl
> set services analytics sensor my-sensor-12 resource
> /junos/system/linecard/fabric/
> set services analytics sensor my-sensor-15 server-name my-grafana-srvr
> set services analytics sensor my-sensor-15 export-name my-exprt-prfl
> set services analytics sensor my-sensor-15 resource
> /junos/system/linecard/interface/logical/usage/
> set services analytics sensor my-sensor-17 server-name my-grafana-srvr
> set services analytics sensor my-sensor-17 export-name my-exprt-prfl
> set services analytics sensor my-sensor-17 resource
> /junos/system/linecard/npu/memory/
> set services analytics sensor my-sensor-18 server-name my-grafana-srvr
> set services analytics sensor my-sensor-18 export-name my-exprt-prfl
> set services analytics sensor my-sensor-18 resource
> /junos/system/linecard/npu/utilization/
> set services analytics sensor my-sensor-19 server-name my-grafana-srvr
> set services analytics sensor my-sensor-19 export-name my-exprt-prfl
> set services analytics sensor my-sensor-19 resource
> /junos/system/linecard/optics/
> set services analytics sensor my-sensor-21 server-name my-grafana-srvr
> set services analytics sensor my-sensor-21 export-name my-exprt-prfl
> set services analytics sensor my-sensor-21 resource
> /junos/system/linecard/services/inline-jflow/
> set services analytics sensor my-sensor-13 server-name my-grafana-srvr
> set services analytics sensor my-sensor-13 export-name my-exprt-prfl
> set services analytics sensor my-sensor-13 resource
> /junos/system/linecard/firewall/
>
> -Aaron
>
> -----Original Message-----
> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf
> Of
> Colton Conor
> Sent: Thursday, April 9, 2020 3:25 PM
> To: Juniper List
> Subject: [j-nsp] Junos Telemetry Interface
>
> Instead of monitoring Juniper equipment by SNMP with 5 minute polling we
> would like to use streaming telemetry to monitor the devices in real-time.
> This requires the Junos Telemetry Interface.
>
> Looking in the Juniper Feature Explorer, Junos Telemetry Interface is not a
> feature, but rater a whole category in the feature explorer, with multiple
> features under it. What feature am I looking for to be able to monitor the
> interfaces in real-time, and see how much bandwidth flows across them
> similar to SNMP?
>
> The ACX platforms only support the Specify Routing Instance for JTI
> feature?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>