Yup – you’re both right – the view actually BROKE Observium – the view disabled too much for Observium to poll at all –

We ended up just going this we found in the forums

(in /opt/observium/config.php)

// Disable EtherLike-MIB

$config['enable_ports_etherlike']       = 0;      # Enable Polling EtherLike-MIB (doubles interface processing time)

// Disable FDB table polling

$config['poller_modules']['fdb-table']                    = 0; 

// Disable ARP table polling

$config['discovery_modules']['arp-table']                    = 0;

Quite a big issue – without this – the 3850 switch CPU was going BONKERS and dropping packets… insane.

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Derek
Sent: Sunday, March 15, 2015 01:09 AM
To: Observium Network Observation System
Subject: Re: [Observium] High CPU on Cisco Switches

You have a lot of VLAN's? You can disable certain types of polling through Observium too. 

On Sat, Mar 14, 2015 at 10:47 PM, Joseph L. Brunner <joe@affirmedsystems.com> wrote:

Team,

We had some cisco switches dropping packets with 99% cpu being polled by Observium.

We had to create a view which hides some arp and routing table objects to bring the CPU back down to normal levels

snmp-server view cutdown at excluded

snmp-server view cutdown snmpUsmMIB excluded

snmp-server view cutdown snmpVacmMIB excluded

snmp-server view cutdown snmpCommunityMIB excluded

snmp-server view cutdown ip.21 excluded

snmp-server view cutdown ip.22 excluded

snmp-server community ourcomm1 view cutdown RO

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