Laurence,

I have this happen frequently at some of our locations that are served via T1, mostly when they're maxing out their bandwidth. There's settings you can change for both the timeout and the retries available, just go into the properties for the device and click the SNMP tab and you can edit them there.

There's also a  couple lines I see in the defaults.inc.php for this, however they are commented out so I'm not sure if they're deprecated or possibly just so it defaults to the individual device settings, as I don't use them. If you want to, add these to your config.php file with whatever values you want:

$config['snmp']['timeout']    = 1;          // timeout in seconds
$config['snmp']['retries']    = 5;          // how many times to retry the query

On Tue, Aug 2, 2016 at 10:53 AM, Laurence Mayer <laurence@istraresearch.com> wrote:

Hello,

Today for no known reason we received the below alert in the "Recent Events" (and via email), everything on the switch appears to have been ok and could not find any issue that should have caused this alert.

6h 36m 15scisco10g1 cisco10g1 Device status changed to Up
6h 36m 16scisco10g1 cisco10g1 Device status changed to Down (snmp)

Is there a timeout that may have caused this that i can increase to avoid false/positives?

Thanks

Laurence

_______________________________________________
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