Hi, I just upgraded from version 0.8.6 to 0.8.7. Everything seemtowork, besides some ups'en. At the moment ihave two insances working, one with 0.8.7 and one with 0.8.6 (the old one) and for some devices , who are only accepting snmp v1,the new version (0.8.7) doesn't poll. this concerns for example : ConnectUPS Web/SNMP Card V3.18. Tested by snmpwalk.
I played with the settings, and none of the version work. So I have my doubt about the versions of snmp in het scripts (in settings when you change it to version 1) and according to me , only version 2c and 3 is accepted
I also tried it with both pollers.
This is from the logs
05/23/2008 04:28:10 PM - SPINE: Poller[0] Host[101] SNMP Result: Host did not respond to SNMP
Anybody who can help ?
grtz,
Johan
upgrade version 0.8.7 / snmp version 1 problems
Moderators: Developers, Moderators
Running 0.8.7a against ~160 devices. Switched from PHP poller to spine to ensure a polling run completes within the cron window. Since then all 6 of the SNMP version 1 devices have been marked down by spine. Error log message is "Host did not respond to SNMP".
Looking at the cacti-spine-0.8.7a/ping.c source I see it tries .1 and then .1.3.6.1.2.1.1.3.0 and then .1.3.6.1.2.1.1.1.0. I'm not sure if it is an artifact of my SNMP libraries (Net SNMP 5.1.2) that .1 returns and odd error message for SNMP version 1 devices on OID .1 (which might be breaking ping.c) ...
# snmpget -v 1 -c xx yy .1
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: ccitt.1
# snmpget -v 1 -c xx yy .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3413665391) 395 days, 2:24:13.91
While a SNMP version 2c enabled device returns ...
# snmpget -v 2c -c xx yy .1
ccitt.1 = No Such Object available on this agent at this OID
# snmpget -v 2c -c xx yy .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (608187581) 70 days, 9:24:35.81
Any help much appreciated.
Matt
Looking at the cacti-spine-0.8.7a/ping.c source I see it tries .1 and then .1.3.6.1.2.1.1.3.0 and then .1.3.6.1.2.1.1.1.0. I'm not sure if it is an artifact of my SNMP libraries (Net SNMP 5.1.2) that .1 returns and odd error message for SNMP version 1 devices on OID .1 (which might be breaking ping.c) ...
# snmpget -v 1 -c xx yy .1
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: ccitt.1
# snmpget -v 1 -c xx yy .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3413665391) 395 days, 2:24:13.91
While a SNMP version 2c enabled device returns ...
# snmpget -v 2c -c xx yy .1
ccitt.1 = No Such Object available on this agent at this OID
# snmpget -v 2c -c xx yy .1.3.6.1.2.1.1.3.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (608187581) 70 days, 9:24:35.81
Any help much appreciated.
Matt
Who is online
Users browsing this forum: No registered users and 2 guests