Quantcast
Viewing all articles
Browse latest Browse all 853

Collect oids for device timeout via zenperfsnmp

Hello,

 

I try to collect metrics via snmp for my one device.

It report 'SNMP agent down - no response received' and 'SNMP agent up' intermittly.

After turnning on debug logging for zen.zenperfsnmp, I found the following staff:

2013-05-31 09:02:57,238 DEBUG zen.collector.scheduler: Task 137.116.165.190 changing state from FETCH_PERF_DATA to RUNNING

2013-05-31 09:02:57,238 DEBUG zen.zenperfsnmp: timeout for 137.116.165.190 [137.116.165.190] oids - ['1.3.6.1.4.1.38420.20.2.3.1.1.11.102.114.101.101.95.109.101.109.111.114.121', '1.3.6.1.4.1.38420.20.1.3.1.1.10.100.105.115.107.95.117.115.97.103.101', '1.3.6.1.4.1.38420.20.5.3.1.1.15.112.114.111.99.101.115.115.101.115.95.99.111.117.110.116', '1.3.6.1.4.1.38420.20.3.3.1.1.12.116.111.116.97.108.95.109.101.109.111.114.121', '1.3.6.1.4.1.38420.20.6.3.1.1.9.99.112.117.95.117.115.97.103.101']

2013-05-31 09:02:57,238 DEBUG zen.zenperfsnmp: 137.116.165.190 [137.116.165.190] some oids still uncollected after 1 tries, trying again with chunk size 1

2013-05-31 09:02:57,238 DEBUG zen.zenperfsnmp: Fetching OID chunk size 1 from 137.116.165.190 [137.116.165.190] - ['1.3.6.1.4.1.38420.20.2.3.1.1.11.102.114.101.101.95.109.101.109.111.114.121']

2013-05-31 09:02:57,239 DEBUG zen.collector.scheduler: Task 137.116.165.190 changing state from RUNNING to FETCH_PERF_DATA

....

2013-05-31 09:05:57,265 DEBUG zen.collector.scheduler: Task 137.116.165.190 changing state from FETCH_PERF_DATA to RUNNING

2013-05-31 09:05:57,265 DEBUG zen.zenperfsnmp: timeout for 137.116.165.190 [137.116.165.190] oids - ['1.3.6.1.4.1.38420.20.1.3.1.1.10.100.105.115.107.95.117.115.97.103.101']

2013-05-31 09:05:57,265 DEBUG zen.zenperfsnmp: 3 consecutive timeouts, abandoning run for 137.116.165.190 [137.116.165.190]

2013-05-31 09:05:57,266 DEBUG zen.zenperfsnmp: Device 137.116.165.190 [137.116.165.190] snmp timed out

 

 

But I can get these file oid successfully.

 

via snmpget:

[zenoss@ zenoss]$ time /usr/bin/snmpget -v3 -l authNoPriv  -a MD5 137.116.165.190 1.3.6.1.4.1.38420.20.2.3.1.1.11.102.114.101.101.95.109.101.109.111.114.121

SNMPv2-SMI::enterprises.38420.20.2.3.1.1.11.102.114.101.101.95.109.101.109.111.114.121 = STRING: "873500"

 

 

real    0m0.392s

user    0m0.052s

sys 0m0.000s

[zenoss@ zenoss]$ time /usr/bin/snmpget -v3 -l authNoPriv -u -a MD5 137.116.165.190 1.3.6.1.4.1.38420.20.1.3.1.1.10.100.105.115.107.95.117.115.97.103.101

SNMPv2-SMI::enterprises.38420.20.1.3.1.1.10.100.105.115.107.95.117.115.97.103.101 = STRING: "37"

 

 

real    0m0.591s

user    0m0.060s

sys 0m0.004s

[zenoss@ zenoss]$ time /usr/bin/snmpget -v3 -l authNoPriv -a MD5 137.116.165.190 1.3.6.1.4.1.38420.20.5.3.1.1.15.112.114.111.99.101.115.115.101.115.95.99.111.117.110.116

SNMPv2-SMI::enterprises.38420.20.5.3.1.1.15.112.114.111.99.101.115.115.101.115.95.99.111.117.110.116 = STRING: "60"

 

 

real    0m1.452s

user    0m0.060s

sys 0m0.000s

[zenoss@ zenoss]$ time /usr/bin/snmpget -v3 -l authNoPriv -a MD5 137.116.165.190 1.3.6.1.4.1.38420.20.3.3.1.1.12.116.111.116.97.108.95.109.101.109.111.114.121

SNMPv2-SMI::enterprises.38420.20.3.3.1.1.12.116.111.116.97.108.95.109.101.109.111.114.121 = STRING: "1878581248"

 

 

real    0m0.347s

user    0m0.052s

sys 0m0.000s

[zenoss@ zenoss]$ time /usr/bin/snmpget -v3 -l authNoPriv -a MD5 137.116.165.190 1.3.6.1.4.1.38420.20.6.3.1.1.9.99.112.117.95.117.115.97.103.101

SNMPv2-SMI::enterprises.38420.20.6.3.1.1.9.99.112.117.95.117.115.97.103.101 = STRING: "0"

 

 

real    0m1.404s

user    0m0.056s

sys 0m0.004s

 

Any hints?


Viewing all articles
Browse latest Browse all 853

Trending Articles