Re: [j-nsp] Junos Telemetry Interface
--- Begin Message --- Note that I'm not speaking for my employer's implementation here. I don't know enough of the code in question to give a deep dive answer into the issue from top of my head. That said, I've spent a number of years working on data aggregation tools in a prior life. Getting a device that has a lot of varying workloads in a non-realtime OS to spit out something on strict timers is often challenging at the best of times. Telemetry in particular often has to be serviced at a rate that means that it's prone to slippage into bins the next sample over. This is usually apparent when you see a zero-bin directly adjacent to a bin that appears to be doubly counted. Longer sampling windows help this. On the producer, sadly, this sometimes means that you simply have more data binned with similar slippage depending on when timers fire. This typically means that the smoothing operations are best done on the consumer of the data. --- Generalities aside, I'll see if I can find someone to comment on this thread. Because I've been the person trying to consume this state, and it'd drive me nuts too! If I had to guess, we're seeing timer and bin size mismatches between the PFE exporter and the RE local aggregator. -- Jeff > On Apr 22, 2020, at 9:06 AM, Martin Tonusoo wrote: > > Hi Aaron, > >> I tried decimals and zero to see what would happen, seems that 1 is the > lowest. > > Looks like it is possible to configure 0 as a reporting-rate > using ephemeral database, but then the device simply does not send any > telemetry data. > > > I also did some further testing with Grafana and it looks like the 5 second > aggregation mentioned in my previous e-mail is too short time-interval for > Junos telemetry data. I built a small setup where the server sent exactly > 10 ICMP "echo request" packets with 1472 byte payload in each second to vMX > router using the ge-0/0/1.88 interface. There was no other traffic on that > link. Telemetry data was exported from the vMX over another link using the > shortest possible "reporting-rate". 30 second screencast with 5 second > aggregation can be seen here: > https://urldefense.com/v3/__https://i.imgur.com/Cfn6Lwp.gif__;!!NEt6yMaO-gk!V6SwreFZy_Qf-A4rbW2HmKNyNClNOcJfKpcmTUiwVIEDW-W8DTh0y9vX4ebhJec$ > ..and with 30 > second aggregation: > https://urldefense.com/v3/__https://i.imgur.com/OSKPSYr.gif__;!!NEt6yMaO-gk!V6SwreFZy_Qf-A4rbW2HmKNyNClNOcJfKpcmTUiwVIEDW-W8DTh0y9vXxxcz-ho$ > With 5 second > aggregation the graph is cleary way too choppy and while it's better with > 30 second interval, then ideally the graph should be a flat line at 120 > kbps. > There are probably technical reasons for this, but it's weird that PFE > sensors telemetry data in Junos is exported that infrequently. Especially > native sensors which are exported by PFE directly. > > > WBR, > Martin > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/juniper-nsp__;!!NEt6yMaO-gk!V6SwreFZy_Qf-A4rbW2HmKNyNClNOcJfKpcmTUiwVIEDW-W8DTh0y9vXvFY7hdc$ --- End Message --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
Hi Aaron, > I tried decimals and zero to see what would happen, seems that 1 is the lowest. Looks like it is possible to configure 0 as a reporting-rate using ephemeral database, but then the device simply does not send any telemetry data. I also did some further testing with Grafana and it looks like the 5 second aggregation mentioned in my previous e-mail is too short time-interval for Junos telemetry data. I built a small setup where the server sent exactly 10 ICMP "echo request" packets with 1472 byte payload in each second to vMX router using the ge-0/0/1.88 interface. There was no other traffic on that link. Telemetry data was exported from the vMX over another link using the shortest possible "reporting-rate". 30 second screencast with 5 second aggregation can be seen here: https://i.imgur.com/Cfn6Lwp.gif ..and with 30 second aggregation: https://i.imgur.com/OSKPSYr.gif With 5 second aggregation the graph is cleary way too choppy and while it's better with 30 second interval, then ideally the graph should be a flat line at 120 kbps. There are probably technical reasons for this, but it's weird that PFE sensors telemetry data in Junos is exported that infrequently. Especially native sensors which are exported by PFE directly. WBR, Martin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
Here's my lab MX960 Mine is currently set at 1 second set services analytics export-profile my-exprt-prfl reporting-rate 1 I tried decimals and zero to see what would happen, seems that 1 is the lowest. {master}[edit] agould@lab-960# set services analytics export-profile my-exprt-prfl reporting-rate Possible completions: Telemetry interval in seconds (0..3600 seconds) {master}[edit] agould@lab-960# set services analytics export-profile my-exprt-prfl reporting-rate .1 ^ Invalid numeric value: '.1' at '.1' {master}[edit] agould@lab-960# set services analytics export-profile my-exprt-prfl reporting-rate .9 ^ Invalid numeric value: '.9' at '.9' {master}[edit] agould@lab-960# set services analytics export-profile my-exprt-prfl reporting-rate 0 {master}[edit] agould@lab-960# show | compare [edit services analytics export-profile my-exprt-prfl] -reporting-rate 1; +reporting-rate 0; {master}[edit] agould@lab-960# commit check re0: [edit services analytics] 'sensor my-sensor-14' reporting-rate of 0 not supported for PFE sensor error: configuration check-out failed -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
Hi Dario, > So I can get the correct values in Grafana in bps, what reporting-rate do you have configured on the Juniper? I configured 1 second interval, but I noticed that at least vMX sent data with 2 and occasionally 3 second intervals. I guess this is because according to https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/export-profile-edit-services-analytics.html the minimum reporting rate for PFE sensors is 2 seconds. > Also in Grafana, what should the derivative value be in seconds? Unfortunately, I no longer have this Grafana setup running, but according to notes for myself I used something like this: SELECT non_negative_derivative(mean("i_octets"),1s)*8 AS "incoming" FROM "octets" WHERE ("ifl" = 'ge-0/0/1.88') AND $timeFilter GROUP BY time(5s) fill(none) WBR, Martin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
e’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.co...@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=Specify%20Routing%20Instance%20for%20JTI> >>>>>> =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 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 &
Re: [j-nsp] Junos Telemetry Interface
On Tue, Apr 14, 2020 at 2:01 PM Martin Tonusoo wrote: > > Hi Dario, > > > This looks really useful, thanks for sharing. Just checking, do I only need > > this script, InfluxDB and Grafana to get traffic graphs? > > That's correct. Thanks - it's working nicely. So I can get the correct values in Grafana in bps, what reporting-rate do you have configured on the Juniper? Also in Grafana, what should the derivative value be in seconds? If I change that I get different results on the graph for bps.. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
Hi Dario, > This looks really useful, thanks for sharing. Just checking, do I only need this script, InfluxDB and Grafana to get traffic graphs? That's correct. WBR, Martin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
On Mon, Apr 13, 2020 at 4:46 AM Aaron Gould 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'm also deploying native JTI at the moment on some MX devices. I have got OpenNTI working, and managed to get traffic graphs working in Grafana using it. I'm now trying to set each part of this up individually without Docker, for a more production ready setup. I've been following this blog: https://openeye.blog/2017/10/31/serving-up-opennti-deconstructed/ I'm trying to get my head around the difference between fluentd and Telegraf, what does each one do, and why are both of these required? ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
On Tue, Apr 14, 2020 at 12:13 AM Martin Tonusoo wrote: > > Telegraf has a built-in input plugin for Juniper Openconfig, so it takes > > like 5 minutes to enable. > > there also seems to be a patch for native sensors: > https://github.com/influxdata/telegraf/pull/6365. Unfortunately, it's not > yet merged. In addition, in order to better understand how the native > sensors work, I wrote a small script for lab usage, which pushes native > sensors data to InfluxDB: https://github.com/tonusoo/jti-to-influxdb Maybe > someone finds this useful. Hi Martin, This looks really useful, thanks for sharing. Just checking, do I only need this script, InfluxDB and Grafana to get traffic graphs? So no fluentd, telegraf, etc? ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
Yepp, then you have to go payed version and buy a HB license per device you want to monitor. /Roger On Mon, Apr 13, 2020 at 11:43 PM Colton Conor wrote: > Healthbot looks interesting. However, most of our Juniper gear we buy is > used, so I doubt we have a support contract on it. Is healthbot still an > option? > > On Mon, Apr 13, 2020 at 4:22 PM Roger Wiklund > wrote: > >> Hi >> >> Check out Juniper Healthbot. It can consume Netconf, SNMP, Syslog, Native >> and OpenConfig, also works with Cisco. >> Still pretty fresh product but has potential. 3.0 should be released >> soonish. Freemium approach where you can use basic features for free as >> long as you have a service contract for the device you want to monitor. >> Payed version has more features. >> >> >> https://www.juniper.net/documentation/en_US/healthbot/topics/topic-map/healthbot-rules-n-playbooks-map.html >> >> note: Some errors in the documentation above that I have flagged, >> OpenConfig, iAgent/Netconfig and SNMP can of course be used both inband and >> out of band. >> >> /Roger >> >> On Mon, Apr 13, 2020 at 11:07 PM Colton Conor >> wrote: >> >>> Roger, >>> >>> Thanks for the information. It seem like most all of these telemetry and >>> flow solutions require service providers to build their own solutions >>> ontop of InfluxDB or Elasticsearch. Do you know if there are any newer NMS >>> platforms our there that are built ontop of InfluxDB or Elasticsearch? >>> Basically, we don't want to do it ourselves, and would prefer to buy a >>> solution. However, talking to someone like SolarWinds for example, and they >>> said they don't currently support streaming telemetry, and its not on their >>> road map at the moment? >>> >>> On Mon, Apr 13, 2020 at 3:23 PM Roger Wiklund >>> wrote: >>> >>>> 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 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 >>>>> geni
Re: [j-nsp] Junos Telemetry Interface
Hi, > Telegraf has a built-in input plugin for Juniper Openconfig, so it takes > like 5 minutes to enable. there also seems to be a patch for native sensors: https://github.com/influxdata/telegraf/pull/6365. Unfortunately, it's not yet merged. In addition, in order to better understand how the native sensors work, I wrote a small script for lab usage, which pushes native sensors data to InfluxDB: https://github.com/tonusoo/jti-to-influxdb Maybe someone finds this useful. WBR, Martin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
Healthbot looks interesting. However, most of our Juniper gear we buy is used, so I doubt we have a support contract on it. Is healthbot still an option? On Mon, Apr 13, 2020 at 4:22 PM Roger Wiklund wrote: > Hi > > Check out Juniper Healthbot. It can consume Netconf, SNMP, Syslog, Native > and OpenConfig, also works with Cisco. > Still pretty fresh product but has potential. 3.0 should be released > soonish. Freemium approach where you can use basic features for free as > long as you have a service contract for the device you want to monitor. > Payed version has more features. > > > https://www.juniper.net/documentation/en_US/healthbot/topics/topic-map/healthbot-rules-n-playbooks-map.html > > note: Some errors in the documentation above that I have flagged, > OpenConfig, iAgent/Netconfig and SNMP can of course be used both inband and > out of band. > > /Roger > > On Mon, Apr 13, 2020 at 11:07 PM Colton Conor > wrote: > >> Roger, >> >> Thanks for the information. It seem like most all of these telemetry and >> flow solutions require service providers to build their own solutions >> ontop of InfluxDB or Elasticsearch. Do you know if there are any newer NMS >> platforms our there that are built ontop of InfluxDB or Elasticsearch? >> Basically, we don't want to do it ourselves, and would prefer to buy a >> solution. However, talking to someone like SolarWinds for example, and they >> said they don't currently support streaming telemetry, and its not on their >> road map at the moment? >> >> On Mon, Apr 13, 2020 at 3:23 PM Roger Wiklund >> wrote: >> >>> 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 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/ >>>> >>>> >&
Re: [j-nsp] Junos Telemetry Interface
Hi Check out Juniper Healthbot. It can consume Netconf, SNMP, Syslog, Native and OpenConfig, also works with Cisco. Still pretty fresh product but has potential. 3.0 should be released soonish. Freemium approach where you can use basic features for free as long as you have a service contract for the device you want to monitor. Payed version has more features. https://www.juniper.net/documentation/en_US/healthbot/topics/topic-map/healthbot-rules-n-playbooks-map.html note: Some errors in the documentation above that I have flagged, OpenConfig, iAgent/Netconfig and SNMP can of course be used both inband and out of band. /Roger On Mon, Apr 13, 2020 at 11:07 PM Colton Conor wrote: > Roger, > > Thanks for the information. It seem like most all of these telemetry and > flow solutions require service providers to build their own solutions > ontop of InfluxDB or Elasticsearch. Do you know if there are any newer NMS > platforms our there that are built ontop of InfluxDB or Elasticsearch? > Basically, we don't want to do it ourselves, and would prefer to buy a > solution. However, talking to someone like SolarWinds for example, and they > said they don't currently support streaming telemetry, and its not on their > road map at the moment? > > On Mon, Apr 13, 2020 at 3:23 PM Roger Wiklund > wrote: > >> 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 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.co...@gmail.com] >>> Sent: Saturday,
Re: [j-nsp] Junos Telemetry Interface
Roger, Thanks for the information. It seem like most all of these telemetry and flow solutions require service providers to build their own solutions ontop of InfluxDB or Elasticsearch. Do you know if there are any newer NMS platforms our there that are built ontop of InfluxDB or Elasticsearch? Basically, we don't want to do it ourselves, and would prefer to buy a solution. However, talking to someone like SolarWinds for example, and they said they don't currently support streaming telemetry, and its not on their road map at the moment? On Mon, Apr 13, 2020 at 3:23 PM Roger Wiklund wrote: > 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 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.co...@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=Specify%20Routing%20Instance%20for%20JTI> >> =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 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 bi
Re: [j-nsp] Junos Telemetry Interface
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 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.co...@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=Specify%20Routing%20Instance%20for%20JTI> > =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 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 sens
Re: [j-nsp] Junos Telemetry Interface
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.co...@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=Specify%20Routing%20Instance%20for%20JTI> =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 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: junip
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=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 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-boun...@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@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface
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-boun...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
Response to old thread and referencing my new thread… “[j-nsp] telemetry analytics - mx960 - npu packet rate concerns” My JTI/OpenNTI systems seems to be continuing to run nicely. I use it when I really need to know some details. In the new thread I mentioned above, I was curious about my CGNat MS-MPC-128G resource utilization and starting digging around in those sensor agent and their data I’ve been receiving in my telem station. I’ll copy and paste from that other thread for convienience. Using my JTI/Chronograf/Grafana web interface I'm trying to understand some of the telemetry analytics data I'm seeing coming from what appears to be the sensor resource of my MX960 corresponding to /junos/system/linecard/npu/utilization/ .. The field seen on chronograf that I'm watching is "npu_util_stats.packets.rate" When using the Chronograf data explorer and picking one MX960 and a certain _seq number (0-14 , I don't know what these are) I'm seeing some significant drops in the graph during peak time (approx. 7 - 10 p.m.) watching "npu_util_stats.packets.rate" with mean function (as opposed to median, count, min, max, etc, etc). In other words, the graph shows a typical ramp-up approaching peak times, and ramp-down during the late night hours.. But about a week ago, I started seeing dramatic drops/sags in the graph during those 7-10 p.m. hours. I'd like to try to figure out what those drops are related to. I'm wondering if this is the MS-MPC-128G npu's in-use for my cgnat.. I've been loading it up quite a bit lately with thousands more subscribers behind it, and am trying to watch how it scales. and if I have any reason for concerns regarding resource load, etc. If you unicast email me, I’ll send you screen shots of my telem graphs that are giving me concern and the sensor agent strings that I’m looking at. Thanks y’all - Aaron From: Colton Conor [mailto:colton.co...@gmail.com] Sent: Monday, November 12, 2018 6:47 AM To: Aaron Cc: beec...@beecher.cc; Juniper List; james.burn...@geant.org Subject: Re: [j-nsp] Junos Telemetry Interface (JTI) Guys, I wanted to follow up and see how things are going with JTI? Also, it has been brought to my attention that OpenNMS supports JTI. I was not aware of that, so I figured I would share with others: https://docs.opennms.org/opennms/branches/develop/guide-admin/guide-admin.html#ga-telemetryd On Thu, Oct 11, 2018 at 12:24 PM Aaron1 wrote: Yes Niall, lets stay in touch. Thanks Tom, I’ll have to look at Panoptes Aaron > On Oct 11, 2018, at 8:18 AM, Tom Beecher wrote: > > Related, my company open sourced a tool we've been working on for network > telemetry at NANOG in Vancouver. I'm 95% sure that a JTI receiver is > functional on our internal builds, but they're still working on a few things > with streaming receivers generally, so it's not yet in the public repo. May > be something that can meet your needs at some point if you wanted to keep an > eye on it. > > https://github.com/yahoo/panoptes > >> On Thu, Oct 11, 2018 at 9:02 AM Niall Donaghy >> wrote: >> Fantastic news Aaron! >> >> That tallies with our experience of deploying the 'bundle' version of >> OpenNTI >> for Junos ST. >> >> We look forward to your shared experiences as you kick the tyres and - >> hopefully - incorporate this into your NMS/procedures. :) >> >> Many thanks, >> Niall >> >> >> -Original Message- >> From: Aaron Gould [mailto:aar...@gvtc.com] >> Sent: 11 October 2018 13:59 >> To: juniper-nsp@puck.nether.net >> Cc: James Burnett ; Niall Donaghy >> ; 'Colton Conor' >> Subject: RE: [j-nsp] Junos Telemetry Interface (JTI) >> >> Wanted to circle back with y'all... I finally got this working...thanks to >> techmocha10 (see below) and my linux coworker genius (Dave), >> >> I'll just copy/paste a post I just made... >> >> https://forums.juniper.net/t5/vMX/Telemetry-data-is-not-streaming-from-Juniper-vMX-17-4R1-16/m-p/375996#M923 >> >> >> I got telemetry streaming working using this site ... I have a couple >> MX960's >> streaming telemetry to the suite of software provided in this Open-NTI >> project >> spoken of on this techmocha blog site. I think my previous problems were >> related to conflicting installs as myself and my coworker had loaded >> individual items and then the open-nti suite (which i understand is a docker >> container with all the items like grafana, fluentd, chronograf, influxdb, >> etc) anyway, we started with a fresh install Ubunto virtual machine and >> *only* loaded Open-NTI and it works. >> >> >> I do not know or under
Re: [j-nsp] Junos Telemetry Interface (JTI)
Guys, I wanted to follow up and see how things are going with JTI? Also, it has been brought to my attention that OpenNMS supports JTI. I was not aware of that, so I figured I would share with others: https://docs.opennms.org/opennms/branches/develop/guide-admin/guide-admin.html#ga-telemetryd On Thu, Oct 11, 2018 at 12:24 PM Aaron1 wrote: > Yes Niall, lets stay in touch. > > Thanks Tom, I’ll have to look at Panoptes > > Aaron > > > On Oct 11, 2018, at 8:18 AM, Tom Beecher wrote: > > > > Related, my company open sourced a tool we've been working on for > network telemetry at NANOG in Vancouver. I'm 95% sure that a JTI receiver > is functional on our internal builds, but they're still working on a few > things with streaming receivers generally, so it's not yet in the public > repo. May be something that can meet your needs at some point if you wanted > to keep an eye on it. > > > > https://github.com/yahoo/panoptes > > > >> On Thu, Oct 11, 2018 at 9:02 AM Niall Donaghy > wrote: > >> Fantastic news Aaron! > >> > >> That tallies with our experience of deploying the 'bundle' version of > OpenNTI > >> for Junos ST. > >> > >> We look forward to your shared experiences as you kick the tyres and - > >> hopefully - incorporate this into your NMS/procedures. :) > >> > >> Many thanks, > >> Niall > >> > >> > >> -Original Message----- > >> From: Aaron Gould [mailto:aar...@gvtc.com] > >> Sent: 11 October 2018 13:59 > >> To: juniper-nsp@puck.nether.net > >> Cc: James Burnett ; Niall Donaghy > >> ; 'Colton Conor' > >> Subject: RE: [j-nsp] Junos Telemetry Interface (JTI) > >> > >> Wanted to circle back with y'all... I finally got this working...thanks > to > >> techmocha10 (see below) and my linux coworker genius (Dave), > >> > >> I'll just copy/paste a post I just made... > >> > >> > https://forums.juniper.net/t5/vMX/Telemetry-data-is-not-streaming-from-Juniper-vMX-17-4R1-16/m-p/375996#M923 > >> > >> > >> I got telemetry streaming working using this site ... I have a couple > MX960's > >> streaming telemetry to the suite of software provided in this Open-NTI > project > >> spoken of on this techmocha blog site. I think my previous problems > were > >> related to conflicting installs as myself and my coworker had > loaded > >> individual items and then the open-nti suite (which i understand is a > docker > >> container with all the items like grafana, fluentd, chronograf, > influxdb, > >> etc) anyway, we started with a fresh install Ubunto virtual machine > and > >> *only* loaded Open-NTI and it works. > >> > >> > >> I do not know or understand all of the innerworkings of it at this > point, but > >> am quickly learning, even while writing this post... I'm currently > using > >> Chronograf hosted at port and browsing the Data Explorer function > and > >> seeing some nice graphs. (I'm wondering if Chrongraf is simply an > alternative > >> to Grafana gui front end, unsure) There seems to be tons of items to > monitor > >> and analyze, and I'm currently only sending the following sensor > resource from > >> the MX960 and there are several more that can be sent > >> /junos/system/linecard/interface/ > >> > >> > >> I am sending the telemetry from the MX960 using UDP transport and GPB > format > >> to port 5 and source port 2 (mx960-1) and 21112 (mx960-2). I'm > unsure > >> that I had to use unique source ports... as I wonder if the source-ip > would > >> have been sufficient to make the streaming sources unique in the > Open-NTI > >> server. > >> > >> > >> Looking at the techmocha pictures, and the "docker ps" command on the > linux > >> server, and now this new-found techmocha link (see "deconstructed" > below) > >> apparently FluentD is the TSDB (time series db) that is > receiving/ingesting > >> the *Native* streaming form of telemetry from my MX960's on udp port > 5 and > >> looks like fluentd hands off that data to InfluxDB port 8086 (which i > think > >> happens internally at that server). (I'm not evening talking about the > other > >> form of jti telemetry using openconfig and grpcI've yet to do that > and > >> don't know why I would exactly...which i beleive is ingested using > telegraf, > >&g
Re: [j-nsp] Junos Telemetry Interface (JTI)
Yes Niall, lets stay in touch. Thanks Tom, I’ll have to look at Panoptes Aaron > On Oct 11, 2018, at 8:18 AM, Tom Beecher wrote: > > Related, my company open sourced a tool we've been working on for network > telemetry at NANOG in Vancouver. I'm 95% sure that a JTI receiver is > functional on our internal builds, but they're still working on a few things > with streaming receivers generally, so it's not yet in the public repo. May > be something that can meet your needs at some point if you wanted to keep an > eye on it. > > https://github.com/yahoo/panoptes > >> On Thu, Oct 11, 2018 at 9:02 AM Niall Donaghy >> wrote: >> Fantastic news Aaron! >> >> That tallies with our experience of deploying the 'bundle' version of >> OpenNTI >> for Junos ST. >> >> We look forward to your shared experiences as you kick the tyres and - >> hopefully - incorporate this into your NMS/procedures. :) >> >> Many thanks, >> Niall >> >> >> -Original Message- >> From: Aaron Gould [mailto:aar...@gvtc.com] >> Sent: 11 October 2018 13:59 >> To: juniper-nsp@puck.nether.net >> Cc: James Burnett ; Niall Donaghy >> ; 'Colton Conor' >> Subject: RE: [j-nsp] Junos Telemetry Interface (JTI) >> >> Wanted to circle back with y'all... I finally got this working...thanks to >> techmocha10 (see below) and my linux coworker genius (Dave), >> >> I'll just copy/paste a post I just made... >> >> https://forums.juniper.net/t5/vMX/Telemetry-data-is-not-streaming-from-Juniper-vMX-17-4R1-16/m-p/375996#M923 >> >> >> I got telemetry streaming working using this site ... I have a couple >> MX960's >> streaming telemetry to the suite of software provided in this Open-NTI >> project >> spoken of on this techmocha blog site. I think my previous problems were >> related to conflicting installs as myself and my coworker had loaded >> individual items and then the open-nti suite (which i understand is a docker >> container with all the items like grafana, fluentd, chronograf, influxdb, >> etc) anyway, we started with a fresh install Ubunto virtual machine and >> *only* loaded Open-NTI and it works. >> >> >> I do not know or understand all of the innerworkings of it at this point, >> but >> am quickly learning, even while writing this post... I'm currently using >> Chronograf hosted at port and browsing the Data Explorer function and >> seeing some nice graphs. (I'm wondering if Chrongraf is simply an >> alternative >> to Grafana gui front end, unsure) There seems to be tons of items to monitor >> and analyze, and I'm currently only sending the following sensor resource >> from >> the MX960 and there are several more that can be sent >> /junos/system/linecard/interface/ >> >> >> I am sending the telemetry from the MX960 using UDP transport and GPB format >> to port 5 and source port 2 (mx960-1) and 21112 (mx960-2). I'm >> unsure >> that I had to use unique source ports... as I wonder if the source-ip would >> have been sufficient to make the streaming sources unique in the Open-NTI >> server. >> >> >> Looking at the techmocha pictures, and the "docker ps" command on the linux >> server, and now this new-found techmocha link (see "deconstructed" below) >> apparently FluentD is the TSDB (time series db) that is receiving/ingesting >> the *Native* streaming form of telemetry from my MX960's on udp port 5 >> and >> looks like fluentd hands off that data to InfluxDB port 8086 (which i think >> happens internally at that server). (I'm not evening talking about the >> other >> form of jti telemetry using openconfig and grpcI've yet to do that and >> don't know why I would exactly...which i beleive is ingested using telegraf, >> unsure) >> >> >> ...the link i followed to deploy open-nti suite >> https://techmocha.blog/2017/06/26/using-opennti-as-a-collector-for-streaming-telemetry-from-juniper-devices-part-1/#comments >> >> >> ...interestingly, i just now found this, which apparently is a way of >> deploying all the components individually... >> https://techmocha.blog/2017/10/31/serving-up-opennti-deconstructed/ >> >> >> >> ___ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
Related, my company open sourced a tool we've been working on for network telemetry at NANOG in Vancouver. I'm 95% sure that a JTI receiver is functional on our internal builds, but they're still working on a few things with streaming receivers generally, so it's not yet in the public repo. May be something that can meet your needs at some point if you wanted to keep an eye on it. https://github.com/yahoo/panoptes On Thu, Oct 11, 2018 at 9:02 AM Niall Donaghy wrote: > Fantastic news Aaron! > > That tallies with our experience of deploying the 'bundle' version of > OpenNTI > for Junos ST. > > We look forward to your shared experiences as you kick the tyres and - > hopefully - incorporate this into your NMS/procedures. :) > > Many thanks, > Niall > > > -Original Message- > From: Aaron Gould [mailto:aar...@gvtc.com] > Sent: 11 October 2018 13:59 > To: juniper-nsp@puck.nether.net > Cc: James Burnett ; Niall Donaghy > ; 'Colton Conor' > Subject: RE: [j-nsp] Junos Telemetry Interface (JTI) > > Wanted to circle back with y'all... I finally got this working...thanks to > techmocha10 (see below) and my linux coworker genius (Dave), > > I'll just copy/paste a post I just made... > > > https://forums.juniper.net/t5/vMX/Telemetry-data-is-not-streaming-from-Juniper-vMX-17-4R1-16/m-p/375996#M923 > > > I got telemetry streaming working using this site ... I have a couple > MX960's > streaming telemetry to the suite of software provided in this Open-NTI > project > spoken of on this techmocha blog site. I think my previous problems were > related to conflicting installs as myself and my coworker had loaded > individual items and then the open-nti suite (which i understand is a > docker > container with all the items like grafana, fluentd, chronograf, influxdb, > etc) anyway, we started with a fresh install Ubunto virtual machine > and > *only* loaded Open-NTI and it works. > > > I do not know or understand all of the innerworkings of it at this point, > but > am quickly learning, even while writing this post... I'm currently using > Chronograf hosted at port and browsing the Data Explorer function and > seeing some nice graphs. (I'm wondering if Chrongraf is simply an > alternative > to Grafana gui front end, unsure) There seems to be tons of items to > monitor > and analyze, and I'm currently only sending the following sensor resource > from > the MX960 and there are several more that can be sent > /junos/system/linecard/interface/ > > > I am sending the telemetry from the MX960 using UDP transport and GPB > format > to port 5 and source port 2 (mx960-1) and 21112 (mx960-2). I'm > unsure > that I had to use unique source ports... as I wonder if the source-ip > would > have been sufficient to make the streaming sources unique in the Open-NTI > server. > > > Looking at the techmocha pictures, and the "docker ps" command on the > linux > server, and now this new-found techmocha link (see "deconstructed" below) > apparently FluentD is the TSDB (time series db) that is > receiving/ingesting > the *Native* streaming form of telemetry from my MX960's on udp port 5 > and > looks like fluentd hands off that data to InfluxDB port 8086 (which i > think > happens internally at that server). (I'm not evening talking about the > other > form of jti telemetry using openconfig and grpcI've yet to do that and > don't know why I would exactly...which i beleive is ingested using > telegraf, > unsure) > > > ...the link i followed to deploy open-nti suite > > https://techmocha.blog/2017/06/26/using-opennti-as-a-collector-for-streaming-telemetry-from-juniper-devices-part-1/#comments > > > ...interestingly, i just now found this, which apparently is a way of > deploying all the components individually... > https://techmocha.blog/2017/10/31/serving-up-opennti-deconstructed/ > > > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
Fantastic news Aaron! That tallies with our experience of deploying the 'bundle' version of OpenNTI for Junos ST. We look forward to your shared experiences as you kick the tyres and - hopefully - incorporate this into your NMS/procedures. :) Many thanks, Niall -Original Message- From: Aaron Gould [mailto:aar...@gvtc.com] Sent: 11 October 2018 13:59 To: juniper-nsp@puck.nether.net Cc: James Burnett ; Niall Donaghy ; 'Colton Conor' Subject: RE: [j-nsp] Junos Telemetry Interface (JTI) Wanted to circle back with y'all... I finally got this working...thanks to techmocha10 (see below) and my linux coworker genius (Dave), I'll just copy/paste a post I just made... https://forums.juniper.net/t5/vMX/Telemetry-data-is-not-streaming-from-Juniper-vMX-17-4R1-16/m-p/375996#M923 I got telemetry streaming working using this site ... I have a couple MX960's streaming telemetry to the suite of software provided in this Open-NTI project spoken of on this techmocha blog site. I think my previous problems were related to conflicting installs as myself and my coworker had loaded individual items and then the open-nti suite (which i understand is a docker container with all the items like grafana, fluentd, chronograf, influxdb, etc) anyway, we started with a fresh install Ubunto virtual machine and *only* loaded Open-NTI and it works. I do not know or understand all of the innerworkings of it at this point, but am quickly learning, even while writing this post... I'm currently using Chronograf hosted at port and browsing the Data Explorer function and seeing some nice graphs. (I'm wondering if Chrongraf is simply an alternative to Grafana gui front end, unsure) There seems to be tons of items to monitor and analyze, and I'm currently only sending the following sensor resource from the MX960 and there are several more that can be sent /junos/system/linecard/interface/ I am sending the telemetry from the MX960 using UDP transport and GPB format to port 5 and source port 2 (mx960-1) and 21112 (mx960-2). I'm unsure that I had to use unique source ports... as I wonder if the source-ip would have been sufficient to make the streaming sources unique in the Open-NTI server. Looking at the techmocha pictures, and the "docker ps" command on the linux server, and now this new-found techmocha link (see "deconstructed" below) apparently FluentD is the TSDB (time series db) that is receiving/ingesting the *Native* streaming form of telemetry from my MX960's on udp port 5 and looks like fluentd hands off that data to InfluxDB port 8086 (which i think happens internally at that server). (I'm not evening talking about the other form of jti telemetry using openconfig and grpcI've yet to do that and don't know why I would exactly...which i beleive is ingested using telegraf, unsure) ...the link i followed to deploy open-nti suite https://techmocha.blog/2017/06/26/using-opennti-as-a-collector-for-streaming-telemetry-from-juniper-devices-part-1/#comments ...interestingly, i just now found this, which apparently is a way of deploying all the components individually... https://techmocha.blog/2017/10/31/serving-up-opennti-deconstructed/ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
Wanted to circle back with y'all... I finally got this working...thanks to techmocha10 (see below) and my linux coworker genius (Dave), I'll just copy/paste a post I just made... https://forums.juniper.net/t5/vMX/Telemetry-data-is-not-streaming-from-Juniper-vMX-17-4R1-16/m-p/375996#M923 I got telemetry streaming working using this site ... I have a couple MX960's streaming telemetry to the suite of software provided in this Open-NTI project spoken of on this techmocha blog site. I think my previous problems were related to conflicting installs as myself and my coworker had loaded individual items and then the open-nti suite (which i understand is a docker container with all the items like grafana, fluentd, chronograf, influxdb, etc) anyway, we started with a fresh install Ubunto virtual machine and *only* loaded Open-NTI and it works. I do not know or understand all of the innerworkings of it at this point, but am quickly learning, even while writing this post... I'm currently using Chronograf hosted at port and browsing the Data Explorer function and seeing some nice graphs. (I'm wondering if Chrongraf is simply an alternative to Grafana gui front end, unsure) There seems to be tons of items to monitor and analyze, and I'm currently only sending the following sensor resource from the MX960 and there are several more that can be sent /junos/system/linecard/interface/ I am sending the telemetry from the MX960 using UDP transport and GPB format to port 5 and source port 2 (mx960-1) and 21112 (mx960-2). I'm unsure that I had to use unique source ports... as I wonder if the source-ip would have been sufficient to make the streaming sources unique in the Open-NTI server. Looking at the techmocha pictures, and the "docker ps" command on the linux server, and now this new-found techmocha link (see "deconstructed" below) apparently FluentD is the TSDB (time series db) that is receiving/ingesting the *Native* streaming form of telemetry from my MX960's on udp port 5 and looks like fluentd hands off that data to InfluxDB port 8086 (which i think happens internally at that server). (I'm not evening talking about the other form of jti telemetry using openconfig and grpcI've yet to do that and don't know why I would exactly...which i beleive is ingested using telegraf, unsure) ...the link i followed to deploy open-nti suite https://techmocha.blog/2017/06/26/using-opennti-as-a-collector-for-streaming-telemetry-from-juniper-devices-part-1/#comments ...interestingly, i just now found this, which apparently is a way of deploying all the components individually... https://techmocha.blog/2017/10/31/serving-up-opennti-deconstructed/ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
Aaron, Yes, OpenNTI includes Grafana. https://techmocha.blog/2017/06/26/using-opennti-as-a-collector-for-streaming-telemetry-from-juniper-devices-part-1/ Doesn't Grafana require alot of work to get all the sensors setup though? AKA its not as simple as an SMNP walk with established NMS software providers? Anyone for Juniper than can comment on the ACX series supporting JTI? An ACX5048 is hardware wise identical to the QFX5100, and the QFX5100 support's JTI. So it has to be just software right? On Fri, Sep 28, 2018 at 9:11 AM Aaron1 wrote: > I think Grafana is also capable of receiving this Telemetry info > > Maybe someone else can share how to make that work > > I’m also wanting to use JTI in ACX, And wondering if that capability is > coming soon > > https://grafana.com/ > > https://github.com/brunorijsman/juniper-grafana > > > > Aaron > > On Sep 28, 2018, at 8:44 AM, Colton Conor wrote: > > Dave, > > Yep, it looks like the video is mentioning SevOne that's them thanks > https://www.sevone.com/streamingdatacollectors > > > > On Fri, Sep 28, 2018 at 8:34 AM Dave Bell wrote: > > Sounds like SevOne to me (https://www.sevone.com/) > > > On Fri, 28 Sep 2018 at 14:08, Colton Conor wrote: > > > Are there any third party network monitoring systems capable of > > interacting > > with Junos Telemetry Interface (JTI)? Many of the third party systems are > > SNMP and ICMP based, but we are looking for more real-time metrics. We > > could set the SNMP polling to intervals of less than a minute, but I > > assume > > that doesn't work very well and why JTI was released? > > > I am aware of OpenNTI, but that doesn't seems to be a commercially > > supported platform and it is missing the elements of a true NMS from what > > I > > can tell. > > > This YouTube video mentions Juniper working with partners, they even > > mention one, but I can't make out the name at time 11:48. Can anyone > > translate? https://www.youtube.com/watch?v=BeprCbmuqLA > > > Does anyone know why the entire ACX line does not have Junos Telemetry > > Interface (JTI)? Is this a coming feature to the ACX platform? > > > Besides SNMP, ICMP, and JTI, are there any other protocols that can be > > used > > for networking monitoring and management in Juniper that I am unaware of? > > ___ > > juniper-nsp mailing list juniper-nsp@puck.nether.net > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
I think Grafana is also capable of receiving this Telemetry info Maybe someone else can share how to make that work I’m also wanting to use JTI in ACX, And wondering if that capability is coming soon https://grafana.com/ https://github.com/brunorijsman/juniper-grafana Aaron > On Sep 28, 2018, at 8:44 AM, Colton Conor wrote: > > Dave, > > Yep, it looks like the video is mentioning SevOne that's them thanks > https://www.sevone.com/streamingdatacollectors > > > >> On Fri, Sep 28, 2018 at 8:34 AM Dave Bell wrote: >> >> Sounds like SevOne to me (https://www.sevone.com/) >> >>> On Fri, 28 Sep 2018 at 14:08, Colton Conor wrote: >>> >>> Are there any third party network monitoring systems capable of >>> interacting >>> with Junos Telemetry Interface (JTI)? Many of the third party systems are >>> SNMP and ICMP based, but we are looking for more real-time metrics. We >>> could set the SNMP polling to intervals of less than a minute, but I >>> assume >>> that doesn't work very well and why JTI was released? >>> >>> I am aware of OpenNTI, but that doesn't seems to be a commercially >>> supported platform and it is missing the elements of a true NMS from what >>> I >>> can tell. >>> >>> This YouTube video mentions Juniper working with partners, they even >>> mention one, but I can't make out the name at time 11:48. Can anyone >>> translate? https://www.youtube.com/watch?v=BeprCbmuqLA >>> >>> Does anyone know why the entire ACX line does not have Junos Telemetry >>> Interface (JTI)? Is this a coming feature to the ACX platform? >>> >>> Besides SNMP, ICMP, and JTI, are there any other protocols that can be >>> used >>> for networking monitoring and management in Juniper that I am unaware of? >>> ___ >>> juniper-nsp mailing list juniper-nsp@puck.nether.net >>> https://puck.nether.net/mailman/listinfo/juniper-nsp >>> >> > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
Dave, Yep, it looks like the video is mentioning SevOne that's them thanks https://www.sevone.com/streamingdatacollectors On Fri, Sep 28, 2018 at 8:34 AM Dave Bell wrote: > Sounds like SevOne to me (https://www.sevone.com/) > > On Fri, 28 Sep 2018 at 14:08, Colton Conor wrote: > >> Are there any third party network monitoring systems capable of >> interacting >> with Junos Telemetry Interface (JTI)? Many of the third party systems are >> SNMP and ICMP based, but we are looking for more real-time metrics. We >> could set the SNMP polling to intervals of less than a minute, but I >> assume >> that doesn't work very well and why JTI was released? >> >> I am aware of OpenNTI, but that doesn't seems to be a commercially >> supported platform and it is missing the elements of a true NMS from what >> I >> can tell. >> >> This YouTube video mentions Juniper working with partners, they even >> mention one, but I can't make out the name at time 11:48. Can anyone >> translate? https://www.youtube.com/watch?v=BeprCbmuqLA >> >> Does anyone know why the entire ACX line does not have Junos Telemetry >> Interface (JTI)? Is this a coming feature to the ACX platform? >> >> Besides SNMP, ICMP, and JTI, are there any other protocols that can be >> used >> for networking monitoring and management in Juniper that I am unaware of? >> ___ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Junos Telemetry Interface (JTI)
Sounds like SevOne to me (https://www.sevone.com/) On Fri, 28 Sep 2018 at 14:08, Colton Conor wrote: > Are there any third party network monitoring systems capable of interacting > with Junos Telemetry Interface (JTI)? Many of the third party systems are > SNMP and ICMP based, but we are looking for more real-time metrics. We > could set the SNMP polling to intervals of less than a minute, but I assume > that doesn't work very well and why JTI was released? > > I am aware of OpenNTI, but that doesn't seems to be a commercially > supported platform and it is missing the elements of a true NMS from what I > can tell. > > This YouTube video mentions Juniper working with partners, they even > mention one, but I can't make out the name at time 11:48. Can anyone > translate? https://www.youtube.com/watch?v=BeprCbmuqLA > > Does anyone know why the entire ACX line does not have Junos Telemetry > Interface (JTI)? Is this a coming feature to the ACX platform? > > Besides SNMP, ICMP, and JTI, are there any other protocols that can be used > for networking monitoring and management in Juniper that I am unaware of? > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp