You can add this to your juniper config instead if you prefer to manage it on the router. 

set snmp filter-interfaces interfaces lsi.*

set snmp filter-interfaces interfaces cbp.*

set snmp filter-interfaces interfaces demux*

set snmp filter-interfaces interfaces pime*

set snmp filter-interfaces interfaces pimd*

set snmp filter-interfaces interfaces pip*

set snmp filter-interfaces interfaces tap*

set snmp filter-interfaces interfaces lo0.16384

set snmp filter-interfaces interfaces "[g|x|a]e.*\.32767"

set snmp filter-interfaces interfaces "et.*\.32767"

set snmp filter-interfaces all-internal-interfaces

---

From: observium [observium-bounces@observium.org] on behalf of Darrell Budic [budic@onholyground.com]
Sent: Wednesday, April 26, 2017 1:06 PM
To: Observium Public Support
Subject: Re: [Observium] Juniper port polling problems

Andrey,

I’ve seen similar issues on my mx-104s, I found some solutions and posted about them previously, check the archives for "artificially high (100%) CPU usage reported from routing engine on Juniper MX-104 w/ 550 interfaces & solution”.

I’ve also added this ignore list into my observium config.php, it overlaps my previous solution somewhat, but after a discovery it won’t even try to poll these anymore, can help if you can’t modify the juniper for some reason. Note the irb regex is commented out, I wanted stats for those but kept it around in case it’s needed. You may need gres, for instance.

#Get rid of bogus JunOS interfaces, most of these are unconfigurable

$config['bad_if_regexp'][] = '/^fxp[0-9]/';     // management interface

$config['bad_if_regexp'][] = '/^cbp[0-9]/';     // no idea

$config['bad_if_regexp'][] = '/^dsc/';          // discard interface

$config['bad_if_regexp'][] = '/^lo[0-9].*/';    // loopback

$config['bad_if_regexp'][] = '/^tap/';          // multicast tunnel

$config['bad_if_regexp'][] = '/^gre/';          // gre interfaces

$config['bad_if_regexp'][] = '/^ipip/';         // ip-in-ip interfaces

$config['bad_if_regexp'][] = '/^pim[a-z]/';     // multicast

$config['bad_if_regexp'][] = '/^mtun/';         // multicast tunnel

$config['bad_if_regexp'][] = '/^em[0-9].*/';    // ethernet management interface

$config['bad_if_regexp'][] = '/^cpb[0-9]/';     // collector interface

$config['bad_if_regexp'][] = '/^demux[0-9]/';   // demux interface

//$config['bad_if_regexp'][] = '/^irb/';          // routing and bridging interface

$config['bad_if_regexp'][] = '/^pip[0-9]/';     // no idea

$config['bad_if_regexp'][] = '/^pp[0-9]/';      // no idea

$config['bad_if_regexp'][] = '/^.*\.[0-9]{5}/'; // auto generated interfaces, e.g. pfd-0/0/0.32567

$config['bad_if_regexp'][] = '/^lc.*/';         // local interface

$config['bad_if_regexp'][] = '/^lsi.*/';        // Internally generated interface

$config['bad_if_regexp'][] = '/^pf[a-z].*/';    // no idea

$config['bad_if_regexp'][] = '/^vme.*/';        // Virtual Chassis management interface

$config['bad_if_regexp'][] = '/^bme.*/';        // Virtual Chassis management interface

$config['bad_if_regexp'][] = '/^jsrv.*/';        // Internal sFlow collector

  -Darrell

On Apr 26, 2017, at 2:06 AM, Andrey <gbox8048@gmail.com> wrote:

Hi, I have observium 0.16.1.7533. It has problems with two machines:  Juniper mx240 with JunOS 15.1R2 and Juniper EX4550-32F with JunOS 12.3R12.4.

This devices very slow polling ports information.

Here I found the same problem: http://jira.observium.org/browse/OBSERVIUM-1695
But there it is written that "junipers have functionally broken SNMP stacks".

Is there any solution to this issue?

Are there any special settings or modules for JunOS ?

Thanks.

<1.png>_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium