Collect oids for device timeout via zenperfsnmp

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73414#73414

--------------------------------------------------------------
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 -u yottaamon -A wlI0kxV8vtdLyfdDjtBkfIvLEEDaIJ -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 yottaamon -A wlI0kxV8vtdLyfdDjtBkfIvLEEDaIJ -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 -u yottaamon -A wlI0kxV8vtdLyfdDjtBkfIvLEEDaIJ -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 -u yottaamon -A wlI0kxV8vtdLyfdDjtBkfIvLEEDaIJ -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 -u yottaamon -A wlI0kxV8vtdLyfdDjtBkfIvLEEDaIJ -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?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73414#73414]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jmp242]

jmp242 [http://community.zenoss.org/people/jmp242] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73417#73417

--------------------------------------------------------------
Maybe try lowering zMaxOIDsPerRequest for that device?

--
James Pulver
ZCA Member
CLASSE Computer Group
Cornell University
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73417#73417]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73433#73433

--------------------------------------------------------------
We've just collected 5 oids for that device. I don't understand why we need to lower zMaxOIDsPerRequest.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73433#73433]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[dhopp]

dhopp [http://community.zenoss.org/people/dhopp] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73399#73399

--------------------------------------------------------------
Your snmpget is using v3.  Have you configured Zenoss to use v3?  It defaults to v2 in Zenoss v4.

--Dennis
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73399#73399]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73430#73430

--------------------------------------------------------------
We've configured v3.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73430#73430]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jmp242]

jmp242 [http://community.zenoss.org/people/jmp242] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73435#73435

--------------------------------------------------------------
I'll need to check, but those are returning STRING, I recall at least through v3 of Zenoss it only accepted INTEGER values... You may have to use command datasources to convert STRING to INTEGER...

--
James Pulver
ZCA Member
CLASSE Computer Group
Cornell University
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73435#73435]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jmp242]

jmp242 [http://community.zenoss.org/people/jmp242] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73437#73437

--------------------------------------------------------------
Ok, I found out that it isn't that issue - Zenoss will try and convert "3" to 3 so I'm not sure why you'd get timeouts - maybe there is a configuration issue?

--
James Pulver
ZCA Member
CLASSE Computer Group
Cornell University
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73437#73437]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73439#73439

--------------------------------------------------------------
I have the same configuration for other devices. They are fine. Not sure why it can not be fine for this device.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73439#73439]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[dhopp]

dhopp [http://community.zenoss.org/people/dhopp] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73401#73401

--------------------------------------------------------------
What type of device is this?
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73401#73401]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73440#73440

--------------------------------------------------------------
It is windows device. I have snmp monitor method to get metrics.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73440#73440]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[XiangJun Wu]

XiangJun Wu [http://community.zenoss.org/people/goafter1981] created the discussion

"Re: Collect oids for device timeout via zenperfsnmp"

To view the discussion, visit: http://community.zenoss.org/message/73404#73404

--------------------------------------------------------------
Finally, I found the issue is due to duplicated engineid.
Is there a way from zenoss to check that?

It is not easy to check them for these windows devices.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/73404#73404]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]