Re: [j-nsp] JunOS Telemetry

Hi Shaffi, The features from 'F' versions are merged in 16.1R1 onwards. So better upgrade to 15.1F6 e.g. for testing telemetry interface. Ivan, On Tue, Apr 11, 2017 at 4:38 PM, wrote: > Actually, not sure your release supports it. Indeed Junos Telemetry > Interface was

Re: [j-nsp] JunOS Telemetry

Thanks Pallavi (and everyone else who responded) Will revisit this when I can move to a newer version. Shaffi -Original Message- From: Pallavi Mahajan [mailto:pall...@juniper.net] Sent: 11 April 2017 5:00 PM To: EXT - david@orange.com ; Shaffi Khan

Re: [j-nsp] JunOS Telemetry

Hi Shaffi, David is correct. In 15.1, JTI is supported only in F branch (15.1F6 is recommended) Thanks, Pallavi On 11/04/17, 9:08 PM, "juniper-nsp on behalf of david@orange.com" wrote: >Actually, not sure your release

Re: [j-nsp] JunOS Telemetry

Actually, not sure your release supports it. Indeed Junos Telemetry Interface was introduced in Junos OS Release 15.1F3. not sure R branch supports it -Message d'origine- De : Shaffi Khan [mailto:shaf...@interxion.com] Envoyé : mardi 11 avril 2017 17:27 À : ROY David DTSI/DERS;

Re: [j-nsp] JunOS Telemetry

Yes, I did try "restart SDN-Telemetry immediately", but there was no effect. Unfortunately I'm not able to try a different version at this point in time. -Original Message- From: david@orange.com [mailto:david@orange.com] Sent: 11 April 2017 3:41 PM To: Shaffi Khan

Re: [j-nsp] JunOS Telemetry

Strange. It works for me. Maybe a bug or a limitation with your version ? Did you try to force SDN-telemetry restart ? -Message d'origine- De : Shaffi Khan [mailto:shaf...@interxion.com] Envoyé : mardi 11 avril 2017 15:57 À : ROY David DTSI/DERS; juniper-nsp@puck.nether.net Objet : RE:

Re: [j-nsp] JunOS Telemetry

Hmm, I'm not seeing any sensors there start shell pfe network fpc2 RMPC platform (1200Mhz QorIQ P2020 processor, 3584MB memory, 512KB flash) NGMPC2(MX-testlab-re0 vty)# show agent sensors ID Name -- Total number of SENSOR = 0 I've just

Re: [j-nsp] JunOS Telemetry

I've tried you config on Junos 16.1R4 and it works for me. David -Message d'origine- De : juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] De la part de Shaffi Khan Envoyé : mardi 11 avril 2017 15:05 À : juniper-nsp@puck.nether.net Objet : [j-nsp] JunOS Telemetry I've just

Re: [j-nsp] JunOS Telemetry

Ok. Could you check at PFE level if sensors are well instanced ? start shell pfe network fpcX show agent sensors ex. show agent sensors Jvision ID Name -- 13222432 sensor-13 5000(300) 13222433 sensor-12 5000(4902)

Re: [j-nsp] JunOS Telemetry

Hi David It seems to be running: show system processes extensive | match agentd 20980 root1 200 717M 5584K select 0 0:05 0.00% agentd 20997 root1 240 720M 4468K select 3 0:00 0.00% stats-agentd Polling is a large number because the value is measured in

Re: [j-nsp] JunOS Telemetry

Hello Does agent is running ? show system processes extensive | match agentd 26812 root 3 200 735M 13136K nanslp 1 0:15 0.00% agentd You could try to restart process : restart SDN-Telemetry immediately I see your polling interval is very high David -Message

[j-nsp] JunOS Telemetry

I've just started investigating using the Juniper telemetry interface for analytics on MX routers, but I'm having some problems getting it running. I'm using the Juniper Open NTI collector, which is up and running (default config, no changes made whatsoever), however it never receives any data,

Re: [j-nsp] ddos protocol protection - IPv4-unclassified

Hey, >> b) LPTS only has 'aggregate' (NPU) level policing, ddos-protection has >> aggregate => ifd => ifl => sub > I don't really see a need for hierarchical policers and besides the uKernel > and RE policers are SW, only the LU has HW policer. It's not really hierarchical, same packet can't

Re: [j-nsp] ddos protocol protection - IPv4-unclassified

> Saku Ytti [mailto:s...@ytti.fi] > Sent: Monday, April 10, 2017 11:37 PM > > Some problems with LPTS > > a) LPTS punted packets are not subject to MQC, so you cannot use interface > policers to limit say say ICMP, BGP etc Yeah this is a huge mess up, taking the control away and not providing