Help with adding SNMP values (V1.8.10)

[SwannMR]

Hi,

I have been using zabbix 1.8.2 for the last year and thought it would great to update to version 1.8.10. I use ubuntu's apt-get install to install the zabbix dependencies.

In 1.8.2 to add new MIBS I had to to add the text file to /usr/share/snmp/mibs/ and restart the zabbix-server to be able to get the items to report a value.

Since updating to 1.8.10 I can't get my new MIBs to work. The pre-load templates works not my new MIBs.

I get the following message from the logs (/var/log/zabbix-server/zabbix_server.log)

snmp_build: unknown failure 1703:20120209:093959.502 Item [vladimir:vibeCallsBlocked[colla type]] error: Cannot find index [vibePeerName] of the OID
[VOIPEX-VIBE-MIB::vibeCallsBlocked["index","vibePeerName","colla type"]]: SNMP error [1]
1692:20120209:094000.873 Item [tvn01-os01:sensor[temp1]] error: Not supported by Zabbix Agent
snmp_build: unknown failure 1692:20120209:094000.886 Item [vladimir:vibeRTTAverage[colla type]] error: Cannot find index [vibePeerName] of the OID [V
OIPEX-VIBE-MIB::vibeRTTAverage["index","vibePeerName","colla type"]]: SNMP error [1]
1693:20120209:094001.394 Item [tvn01-os01:sensor[temp2]] error: Not supported by Zabbix Agent
snmp_build: unknown failure 1693:20120209:094001.407 Item [vladimir:vibeRXJitterAverage[colla type]] error: Cannot find index [vibePeerName] of the O
ID [VOIPEX-VIBE-MIB::vibeRXJitterAverage["index","vibePeerName","colla type"]]: SNMP error [1]
snmp_build: unknown failure 1694:20120209:094002.084 Item [vladimir:vibeTXJitterAverage[colla type]] error: Cannot find index [vibePeerName] of the O
ID [VOIPEX-VIBE-MIB::vibeTXJitterAverage["index","vibePeerName","colla type"]]: SNMP error [1]

I tried research snmp_build but I am not completely sure what it does.

Any help or comments on the above is much appreciated.

Thanks,

[SwannMR]

This problem is related to an indexing issue.

I know this IOD VOIPEX-VIBE-MIB::vibeCallsInProgress["index","vibePeerName","colla type"] works in zabbix 1.8.1 and 1.8.2

Read in the forums about an similar issue but that was to do with dynamic indexes only working with an OID that returns values of type STRING.

https://support.zabbix.com/browse/ZBX-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

They say the problem is fixed in svn 1.8.11

[SwannMR]

Upgrading had little affect

Increased the debugging to 4 and now and now I can start debugging.


1865:20120210:171958.877 In snmp_open_session()
1865:20120210:171958.877 SNMP [[email protected]:161:161]
1865:20120210:171958.877 End of snmp_open_session()
1865:20120210:171958.877 Special processing
1865:20120210:171958.877 method:index
1865:20120210:171958.877 oid_index:vibePeerName
1865:20120210:171958.877 index_value:colla type
1865:20120210:171958.878 In snmp_normalize(oid:vibePeerName)
1865:20120210:171958.878 End of snmp_normalize():vibePeerName
1865:20120210:171958.878 In cache_get_snmp_index(oid:vibePeerName,value:colla type)
1865:20120210:171958.878 End of cache_get_snmp_index(index:0):FAIL
1865:20120210:171958.878 In snmp_get_index(oid:vibePeerName,value:colla type)
1865:20120210:171958.891 snmp_get_index: snmp_pdu_create()


Looks like the snmp calls/checks are generated in checks_snmp.c

[MrKen]

A couple of things you could try:

Check snmp.conf (mine is at /usr/share/snmp/snmp.conf) and check that snmp knows about your mibs. I use the following:

mibs +ALL

If you change snmp.conf, be sure to restart snmpd.


There have been a number of posts over the years reporting similar problems, one of them suggests:

Edit "/usr/local/etc/zabbix/zabbix_server.conf"

comment out "SourceIP=x.x.x.x"

restart zabbix and wallah snmp starts working!

And others have reported compatibility problems with net-snmp 5.5

Hope that helps some.

MrKen


//Off topic - Has anyone googled "current temperature riga latvia"?

Brrrrrrrr!!//

[SwannMR]

Thanks for commenting,

I "solved" the issue

If I setup the SNMP OID =

VOIPEX-VIBE-MIB::vibeCallsBlocked["index",".1.3.6.1.4.1.31030.1.2.1.1.23","colla type"]

as appose to...

VOIPEX-VIBE-MIB::vibeCallsBlocked["index","vibePeerName","colla type"]

Starting digging around in checks_snmp.c and this specifically at the call for cache_get_snmp_index as this looks like the first check the code runs for indexes

1865:20120210:171958.877 In snmp_open_session()
1865:20120210:171958.877 SNMP [[email protected]:161:161]
1865:20120210:171958.877 End of snmp_open_session()
1865:20120210:171958.877 Special processing
1865:20120210:171958.877 method:index
1865:20120210:171958.877 oid_index:vibePeerName
1865:20120210:171958.877 index_value:colla type
1865:20120210:171958.878 In snmp_normalize(oid:vibePeerName)
1865:20120210:171958.878 End of snmp_normalize():vibePeerName
1865:20120210:171958.878 In
cache_get_snmp_index(oid:vibePeerName,value:colla type)

1865:20120210:171958.878 End of cache_get_snmp_index(index:0):FAIL

1865:20120210:171958.878 In snmp_get_index(oid:vibePeerName,value:colla type)
1865:20120210:171958.891 snmp_get_index: snmp_pdu_create()

This reveal the code.

static int cache_get_snmp_index(DC_ITEM *item, char *oid, char *value, int *index)
{
const char *__function_name = "cache_get_snmp_index";
int i, res = FAIL;
zbx_snmp_index_t s;

assert(index);

*index = 0;

zabbix_log(LOG_LEVEL_DEBUG, "In %s(oid:%s,value:%s)", __function_name, oid, value);

It looks like the index is an integer. I am NOT a programmer but looking at the code gave me the idea to try using the OID with numerals instead of a string. Not that the index I passed was an integer - this probably is irrelevant

I was trying to read up on passing values from the command line but since I have my data coming through I probably won't get around to this.

If I have some free time I will investigate further.

Thanks