TECHZEN Zenoss User Community ARCHIVE  

Zenmodeler timeouts via SNMP

Subject: Zenmodeler timeouts via SNMP
Author: Thomas Luther
Posted: 2018-07-24 04:13

Hi

We have upgraded/patched our zenoss core 4.2.5 to RPS 743 + at few patches to make it work. Everything seems to be up and running, but one thing still causes issues.

When zenmodeler starts up (once a day), we will get a number of "SNMP agent down - No response received" events from miscellaneous devices. SNMP does work and if I trigger a manuel model it will clear the event. We do not see SNMP Agent down events from other daemons than zenmodeler, so I suspect that zenmodeler has changed behavior rather than we actually do have a network problem.


------------------------------
Thomas Luther
Senior Consultant
Netic A/S
------------------------------


Subject: RE: Zenmodeler timeouts via SNMP
Author: Thomas Luther
Posted: 2018-07-24 04:31

After searching the logs I found one host which timed out:
zenmodeler.log:2018-07-24 10:26:00,497 INFO zen.ZenModeler: Start collecting for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,498 INFO zen.ZenModeler: Starting collection for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,499 INFO zen.ZenModeler: No WMI plugins found for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,501 INFO zen.ZenModeler: No Python plugins found for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,503 INFO zen.ZenModeler: No command plugins found for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,504 INFO zen.ZenModeler: SNMP collection device console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,505 INFO zen.ZenModeler: Adding SNMP collector client for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,508 INFO zen.ZenModeler: No portscan plugins found for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:00,508 INFO zen.ZenModeler: Running 4 clients: {'another.hostname.tld': [<SnmpClient.SnmpClient object at 0xfeecf90>], 'console.hostname.tld': [<SnmpClient.SnmpClient object at 0xc8c7f10>], 'anotherone.hostname.tld': [<SnmpClient.SnmpClient object at 0x1963bad0>], 'dc4-
zenmodeler.log:2018-07-24 10:26:09,506 INFO zen.SnmpClient: Device timed out: SNMP info for console.hostname.tld at 172.2x.x.yyy:161 timeout: 3.0 tries: 3 version: v2c community: public
zenmodeler.log:2018-07-24 10:26:09,507 INFO zen.SnmpClient: snmp client finished collection for console.hostname.tld
zenmodeler.log:2018-07-24 10:26:09,507 WARNING zen.SnmpClient: Device console.hostname.tld timed out: are your SNMP settings correct?
zenmodeler.log:2018-07-24 10:26:09,507 INFO zen.ZenModeler: No change in configuration detected for console.hostname.tld by <SnmpClient.SnmpClient object at 0xc8c7f10>
zenmodeler.log:2018-07-24 10:26:09,507 INFO zen.ZenModeler: <SnmpClient.SnmpClient object at 0xc8c7f10> client console.hostname.tld finished


------------------------------
Thomas Luther
Senior Consultant
Netic A/S
------------------------------


Subject: RE: Zenmodeler timeouts via SNMP
Author: Jay Stanley
Posted: 2018-07-24 08:19

Try playing with the snmp settings.. I usually do a low number for timeout and a higher number for retries.

Usually a timeout of 1 or 2 sec, with retries at 5.

Might want to try lowering the maxOid per request as well.

------------------------------
jstanley
------------------------------


< Previous
Switching between SNMP v2c and v3
  Next
Regular restarts of containers 5/6.x
>