Re: [j-nsp] SNMP very slow on MX10003
You hit sometimes high response time ( > 14 secs) to collect stats of AE's
units. Could you correlate this timestamp with significant changes on the
router of routing events ?
-Message d'origine-
De : Leon Kramer [mailto:leonkra...@gmail.com]
Envoyé : lundi 25 mai 2020 18:42
À : ROY David DTSI/DERS; juniper-nsp@puck.nether.net
Objet : Re: [j-nsp] SNMP very slow on MX10003
> show snmp stats-response-statistics
Average response time statistics:
StatsStatsAverage
Type ResponsesResponse
Time (ms)
ifd(non ae) 15311162 5.60
ifd(ae) 482105 34.68
ifl(non ae) 5930128 5.96
ifl(ae) 74751690 8.80
firewall 66199433 10.87
Bucket statistics:
Bucket Stats
Type(ms) Responses
0 - 10 117512092
11 - 50 36891316
51 - 100 3645978
101 - 2001647536
201 - 5001330240
501 - 1000 889495
1001 - 2000 707479
2001 - 5000 40989
More than 5001 9393
Bad responses:
ResponseRequestStats Key
Time Type
(ms)(UTC)
14048.002020-04-30 02:26:36ifl(ae)713
13649.322020-05-06 16:50:12ifl(ae)1319
13649.032020-05-06 16:50:12ifl(ae)1320
13648.822020-05-06 16:50:12ifl(ae)1321
13648.592020-05-06 16:50:12ifl(ae)1322
13648.382020-05-06 16:50:12ifl(ae)1323
13647.942020-05-06 16:50:12ifl(ae)1324
13647.722020-05-06 16:50:12ifl(ae)1325
12174.382020-05-19 07:08:22ifl(ae)1517
12145.672020-05-06 16:53:38ifl(ae)3743
12145.422020-05-06 16:53:38ifl(ae)3744
12145.082020-05-06 16:53:38ifl(ae)3745
12144.832020-05-06 16:53:38ifl(ae)3786
12144.522020-05-06 16:53:38ifl(ae)3787
12144.272020-05-06 16:53:38ifl(ae)3788
12144.052020-05-06 16:53:38ifl(ae)3789
12143.772020-05-06 16:53:38ifl(ae)3790
12143.492020-05-06 16:53:38ifl(ae)3791
12143.222020-05-06 16:53:38ifl(ae)3792
12143.002020-05-06 16:53:38ifl(ae)3793
Am Mo., 25. Mai 2020 um 18:32 Uhr schrieb :
>
> Hello
>
> Could you issue this command & share the output : show snmp
> stats-response-statistics
>
> Otherwise, we use telemetry to collect, among other things, interface stats.
>
> David
>
>
> -Message d'origine-
> De : juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] De la part de
> Leon Kramer
> Envoyé : lundi 25 mai 2020 18:26
> À : juniper-nsp@puck.nether.net
> Objet : [j-nsp] SNMP very slow on MX10003
>
> Hello,
>
> we meter approximately 500 logical subinterface counters (e.g. ae0.95,
> ae0.96, etc) of our Juniper MX10003. While this works it is also too
> slow as we fetch the data every 60 seconds.
>
> snmpbulkwalks of IF-MIB::ifHCInOctets and IF-MIB::ifHCOutOctets take
> anything from 1 to 180 seconds.
>
> The time it takes increases noticeably as more subinterfaces are configured.
>
> I know Juniper is not known for fast SNMP queries, but is there
> anything you can do to increase performance? 500 interfaces should
> really not be too much for a fairly new router imho.
> We already have some interface filters in place, but apparently they
> are not sufficient.
>
> If you think that SNMP is too slow, what alternative can you recommend
> for fetching interface counters?
>
> Thank you for your help.
>
>
> Kind Regards
> Leon Kramer
>
>
> > show version
> Model: mx10003
> Junos: 18.4R2-S3
>
>
> > show configuration snmp
> interface [ fxp0.0 ];
> filter-interfaces {
> interfaces {
> "fe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> "xe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> "ge-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> "et-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> }
> all-internal-interfaces;
> }
> filter-duplicates;
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> routing-instance-access;
> ___
> junip
Re: [j-nsp] SNMP very slow on MX10003
> show snmp stats-response-statistics
Average response time statistics:
StatsStatsAverage
Type ResponsesResponse
Time (ms)
ifd(non ae) 15311162 5.60
ifd(ae) 482105 34.68
ifl(non ae) 5930128 5.96
ifl(ae) 74751690 8.80
firewall 66199433 10.87
Bucket statistics:
Bucket Stats
Type(ms) Responses
0 - 10 117512092
11 - 50 36891316
51 - 100 3645978
101 - 2001647536
201 - 5001330240
501 - 1000 889495
1001 - 2000 707479
2001 - 5000 40989
More than 5001 9393
Bad responses:
ResponseRequestStats Key
Time Type
(ms)(UTC)
14048.002020-04-30 02:26:36ifl(ae)713
13649.322020-05-06 16:50:12ifl(ae)1319
13649.032020-05-06 16:50:12ifl(ae)1320
13648.822020-05-06 16:50:12ifl(ae)1321
13648.592020-05-06 16:50:12ifl(ae)1322
13648.382020-05-06 16:50:12ifl(ae)1323
13647.942020-05-06 16:50:12ifl(ae)1324
13647.722020-05-06 16:50:12ifl(ae)1325
12174.382020-05-19 07:08:22ifl(ae)1517
12145.672020-05-06 16:53:38ifl(ae)3743
12145.422020-05-06 16:53:38ifl(ae)3744
12145.082020-05-06 16:53:38ifl(ae)3745
12144.832020-05-06 16:53:38ifl(ae)3786
12144.522020-05-06 16:53:38ifl(ae)3787
12144.272020-05-06 16:53:38ifl(ae)3788
12144.052020-05-06 16:53:38ifl(ae)3789
12143.772020-05-06 16:53:38ifl(ae)3790
12143.492020-05-06 16:53:38ifl(ae)3791
12143.222020-05-06 16:53:38ifl(ae)3792
12143.002020-05-06 16:53:38ifl(ae)3793
Am Mo., 25. Mai 2020 um 18:32 Uhr schrieb :
>
> Hello
>
> Could you issue this command & share the output : show snmp
> stats-response-statistics
>
> Otherwise, we use telemetry to collect, among other things, interface stats.
>
> David
>
>
> -Message d'origine-
> De : juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] De la part de
> Leon Kramer
> Envoyé : lundi 25 mai 2020 18:26
> À : juniper-nsp@puck.nether.net
> Objet : [j-nsp] SNMP very slow on MX10003
>
> Hello,
>
> we meter approximately 500 logical subinterface counters (e.g. ae0.95,
> ae0.96, etc) of our Juniper MX10003. While this works it is also too
> slow as we fetch the data every 60 seconds.
>
> snmpbulkwalks of IF-MIB::ifHCInOctets and IF-MIB::ifHCOutOctets take
> anything from 1 to 180 seconds.
>
> The time it takes increases noticeably as more subinterfaces are configured.
>
> I know Juniper is not known for fast SNMP queries, but is there
> anything you can do to increase performance? 500 interfaces should
> really not be too much for a fairly new router imho.
> We already have some interface filters in place, but apparently they
> are not sufficient.
>
> If you think that SNMP is too slow, what alternative can you recommend
> for fetching interface counters?
>
> Thank you for your help.
>
>
> Kind Regards
> Leon Kramer
>
>
> > show version
> Model: mx10003
> Junos: 18.4R2-S3
>
>
> > show configuration snmp
> interface [ fxp0.0 ];
> filter-interfaces {
> interfaces {
> "fe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> "xe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> "ge-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> "et-[0-9]/[0-9]/[0-9]+\.[0-9]+";
> }
> all-internal-interfaces;
> }
> filter-duplicates;
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> community xxx {
> authorization read-only;
> routing-instance mgmt_junos;
> }
> routing-instance-access;
> ___
> juniper-nsp mailing list juniper-nsp@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,
Re: [j-nsp] SNMP very slow on MX10003
Hi, On 25.05.2020 18:25, Leon Kramer wrote: If you think that SNMP is too slow, what alternative can you recommend for fetching interface counters? Probably the canonical answer these days is streaming telemetry which can be done directly from the PFE for a lot of counters. In a former life when SNMP got too slow we sometimes switches to screenscraping "show interfaces | display XML" via SSH/netconf. But this would only help if the data itself is presented fast enough. We had boxes where presenting thh data itself towards the cli/SNMP agent was the bottleneck so the method of pulling it made no difference. -- Kind Regards Tobias Heister ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] SNMP very slow on MX10003
Hello
Could you issue this command & share the output : show snmp
stats-response-statistics
Otherwise, we use telemetry to collect, among other things, interface stats.
David
-Message d'origine-
De : juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] De la part de
Leon Kramer
Envoyé : lundi 25 mai 2020 18:26
À : juniper-nsp@puck.nether.net
Objet : [j-nsp] SNMP very slow on MX10003
Hello,
we meter approximately 500 logical subinterface counters (e.g. ae0.95,
ae0.96, etc) of our Juniper MX10003. While this works it is also too
slow as we fetch the data every 60 seconds.
snmpbulkwalks of IF-MIB::ifHCInOctets and IF-MIB::ifHCOutOctets take
anything from 1 to 180 seconds.
The time it takes increases noticeably as more subinterfaces are configured.
I know Juniper is not known for fast SNMP queries, but is there
anything you can do to increase performance? 500 interfaces should
really not be too much for a fairly new router imho.
We already have some interface filters in place, but apparently they
are not sufficient.
If you think that SNMP is too slow, what alternative can you recommend
for fetching interface counters?
Thank you for your help.
Kind Regards
Leon Kramer
> show version
Model: mx10003
Junos: 18.4R2-S3
> show configuration snmp
interface [ fxp0.0 ];
filter-interfaces {
interfaces {
"fe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
"xe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
"ge-[0-9]/[0-9]/[0-9]+\.[0-9]+";
"et-[0-9]/[0-9]/[0-9]+\.[0-9]+";
}
all-internal-interfaces;
}
filter-duplicates;
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
routing-instance-access;
___
juniper-nsp mailing list juniper-nsp@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.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] SNMP very slow on MX10003
Hello,
we meter approximately 500 logical subinterface counters (e.g. ae0.95,
ae0.96, etc) of our Juniper MX10003. While this works it is also too
slow as we fetch the data every 60 seconds.
snmpbulkwalks of IF-MIB::ifHCInOctets and IF-MIB::ifHCOutOctets take
anything from 1 to 180 seconds.
The time it takes increases noticeably as more subinterfaces are configured.
I know Juniper is not known for fast SNMP queries, but is there
anything you can do to increase performance? 500 interfaces should
really not be too much for a fairly new router imho.
We already have some interface filters in place, but apparently they
are not sufficient.
If you think that SNMP is too slow, what alternative can you recommend
for fetching interface counters?
Thank you for your help.
Kind Regards
Leon Kramer
> show version
Model: mx10003
Junos: 18.4R2-S3
> show configuration snmp
interface [ fxp0.0 ];
filter-interfaces {
interfaces {
"fe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
"xe-[0-9]/[0-9]/[0-9]+\.[0-9]+";
"ge-[0-9]/[0-9]/[0-9]+\.[0-9]+";
"et-[0-9]/[0-9]/[0-9]+\.[0-9]+";
}
all-internal-interfaces;
}
filter-duplicates;
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
community xxx {
authorization read-only;
routing-instance mgmt_junos;
}
routing-instance-access;
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
