snmpget fails, can I use snmpwalk instead?

[aleksashka]

I found that I can monitor temperature via .1.3.6.1.4.1.9.9.13.1.3.1.3 OID, but it cannot be acquired using snmpget:

Code: Select all

aa@alexandr-debian-test:~$ snmpget -v2c -cTEST 192.168.255.2 .1.3.6.1.4.1.9.9.13.1.3.1.3
iso.3.6.1.4.1.9.9.13.1.3.1.3 = No Such Instance currently exists at this OID

while snmpwalk works fine:

Code: Select all

aa@alexandr-debian-test:~$ snmpwalk -v2c -cTEST 192.168.255.2 .1.3.6.1.4.1.9.9.13.1.3.1.3
iso.3.6.1.4.1.9.9.13.1.3.1.3.1005 = Gauge32: 44

I would use .1.3.6.1.4.1.9.9.13.1.3.1.3.1005 in data template, but another device is using another value:

Code: Select all

aa@alexandr-debian-test:~$ snmpwalk -v2c -cTEST 192.168.112.134 .1.3.6.1.4.1.9.9.13.1.3.1.3
iso.3.6.1.4.1.9.9.13.1.3.1.3.1006 = Gauge32: 17

and I don't want to create different templates for all devices (as a workaround I might try to check Use Per-Data Source Value (Ignore this Value) for OID in temperature template, but I'm pretty sure there should be a better way ).
So here is my question: Is it possible to ask Cacti to use snmpwalk and if it returns multiple values use the first one?

P.S. Cacti Data Queries tutorials start with SNMP table which seems to be inapplicable in this case.

BTW, routers (compared to switches above) return multiple values and to graph two values I created two data templates with needed OIDs and one graph template to show both data templates (I really hope that this can be done using single data template ):

Code: Select all

aa@alexandr-debian-test:~$ snmpwalk -v2c -cTEST 192.168.255.1 .1.3.6.1.4.1.9.9.13.1.3.1.3
iso.3.6.1.4.1.9.9.13.1.3.1.3.1 = Gauge32: 60
iso.3.6.1.4.1.9.9.13.1.3.1.3.2 = Gauge32: 29
iso.3.6.1.4.1.9.9.13.1.3.1.3.3 = Gauge32: 34
iso.3.6.1.4.1.9.9.13.1.3.1.3.4 = Gauge32: 22
iso.3.6.1.4.1.9.9.13.1.3.1.3.5 = Gauge32: 23