[j-nsp] JunOS Telemetry

[david.roy at orange.com]

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)
   13222434  sensor-11             5000(1348)
   13222439  sensor-14             5000(843)
   13222443  sensor-18             0(0)
   13222464  sensor-23             5000(300)
   13222465  sensor-22             5000(4001)
   13222466  sensor-21             5000(1348)
   13222471  sensor-24             5000(843)
   13222475  sensor-28             0(0)
  129585707  __default_fabric_sensor__  5000(3972)

Total number of jvision SENSORs = 11


-----Message d'origine-----
De : Shaffi Khan [mailto:shaffik at interxion.com] 
Envoyé : mardi 11 avril 2017 15:35
À : ROY David DTSI/DERS; juniper-nsp at puck.nether.net
Objet : RE: [j-nsp] JunOS Telemetry

Hi David

It seems to be running:

show system processes extensive | match agentd
20980 root        1  20    0   717M  5584K select  0   0:05   0.00% agentd
20997 root        1  24    0   720M  4468K select  3   0:00   0.00% stats-agentd

Polling is a large number because the value is measured in nano seconds:

{master}[edit services analytics sensor test-sensor] testlab at MXtestlab# set polling-interval ?
Possible completions:
  <polling-interval>   Define sensor polling interval in nano secs (nanoseconds)


So I'm polling every 0.1 seconds.

Simarly, reporting-rate under export-profile is measured in milliseconds, so I'm reporting every second.

 

-----Original Message-----
From: david.roy at orange.com [mailto:david.roy at orange.com]
Sent: 11 April 2017 2:24 PM
To: Shaffi Khan <shaffik at interxion.com>; juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] JunOS Telemetry

Hello

Does agent is running ?

show system processes extensive | match agentd
26812 root          3  20    0   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 d'origine-----
De : juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] De la part de Shaffi Khan Envoyé : mardi 11 avril 2017 15:05 À : juniper-nsp at puck.nether.net Objet : [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, as confirmed by a tcpdump on the box.

My setup is thus:

testlab at MXtestlab # run show version
Hostname: MXtestlab
Model: mx240
Junos: 15.1R4-S2.1

sensor test-sensor {
    server-name open-nti;
    export-name test-telemetry;
    polling-interval 100000000;
    resource /junos/system/linecard/interface/;
}
streaming-server open-nti {
    remote-address 10.100.0.127;
    remote-port 50000;
}
export-profile test-telemetry {
    local-address 10.100.0.96;
    local-port 30010;
    reporting-rate 1000;
    format gpb;
    transport udp;
}

The problem I see is that "show agent sensors" never reports a sensor:
testlab at MXtestlab# run show agent sensors

{master}[edit services analytics]

I've read over the Juniper docs and can't see anything obvious that I'm missing, however I'm sure it is something simple.

If anyone has any idea's I'd love to hear them!

TIA

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.