Proxy 2.0.8 SNMP - All Responses:0

[avenn]

Hello,

Trying to get SNMP data from remote LAN devices via same site remote zabbix proxy 2.0.8. Connected via open VPN.

Proxy logs at debug level 4 suggest request gets through however response for a variety of OIDs appears to be just zero:

get_snmp() snmp_synch_response():0

When I SNMP walk from the proxy to the SNMP device that value returned is accurate:

snmpwalk -v2c -c public 192.168.0.2 .1.3.6.1.2.1.2.2.1.16.1
iso.3.6.1.2.1.2.2.1.16.1 = Counter32: 63053571

Directions on the forums suggest my setup is accurate?

Regards

Aidan

Proxy log extract:

29049:20131011:133742.554 In get_value_snmp() key:'ifOutOctects' oid:'.1.3.6.1.2.1.2.2.1.16.1'
29049:20131011:133742.556 In snmp_open_session()
29049:20131011:133742.559 End of snmp_open_session()
29049:20131011:133742.561 In snmp_normalize(oid:.1.3.6.1.2.1.2.2.1.16.1)
29049:20131011:133742.563 End of snmp_normalize():.1.3.6.1.2.1.2.2.1.16.1
29049:20131011:133742.564 In get_snmp() oid:'.1.3.6.1.2.1.2.2.1.16.1'
29049:20131011:133742.576 get_snmp() snmp_synch_response():0
29049:20131011:133742.578 In snmp_set_value()
29049:20131011:133742.579 End of snmp_set_value():SUCCEED
29049:20131011:133742.581 End of get_snmp():SUCCEED
29049:20131011:133742.582 In snmp_close_session()
29049:20131011:133742.584 End of snmp_close_session()
29049:20131011:133742.586 End of get_value_snmp():SUCCEED
29048:20131011:133743.071 query [txnlev:0] [select hostid,available,error,snmp_available,snmp_error,i pmi_available,ipmi_error,jmx_available,jmx_error from hosts where status in (0,1)]

[avenn]

Hi,

UPDATE

upgrade/recompiled to 2.0.9 and attempting to get SNMP data from server - no luck. Using own snmp items and zabbix templates.

Update net-snmp to latest LTS - no luck.

Zabbix sender to zabbix is fine - logging great.

snmpwalk - fine.

running on deb 7.1

strange - any ideas?

Regards

Aidan

[avenn]

NOT Really SOLVED

As it was only an experimental server I switched back to ubuntu 12 04 LTS - everything okay now.

While researching this issue I came across a number of similar issues in relation to debian and zabbix. Probably a fix but could not find and time was ticking on!