Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
I have run in to a potential problem with the cactid snmp poller.
We are having some issues with graphing some ethernet interfaces... the snmp interface statistics query seems to work fine, but when the poller returns the data the counter value is being thrown in to the log (when I enable full logging) as a 0 value.
Is this something to do with the rather large index number? or something else? Everything else is fine, just certain interfaces on this one specific type of router that is giving very large index values?
I assume then that people are equally as stumped about this as I am?
If I were to try and see what was causing this issue myself by going to the cactid source, would anyone have any idea how I could tell cactid on a 'test' system to poll only one specific device (should I modify the snmp code and put some debug information in it so that I can see what's going on) ?
Paul Thexton wrote:I assume then that people are equally as stumped about this as I am?
Some might be... Not me.. I'm just late..
Double check that the device is showing an up status on the device list, which I think it is. Now, when you edit the device, is it's snmp version set to SNMPv2? Version 2 is needed for 64-bit counters and depending on the agent, it will respond on that OID even on SNMPv1, but with the wrong value.
[size=117][i][b]Tony Roman[/b][/i][/size]
[size=84][i]Experience is what causes a person to make new mistakes instead of old ones.[/i][/size]
[size=84][i]There are only 3 way to complete a project: Good, Fast or Cheap, pick two.[/i][/size]
[size=84][i]With age comes wisdom, what you choose to do with it determines whether or not you are wise.[/i][/size]
Yeah - device status shows as up and SNMPv2 is being used - the interfaces that aren't working have only the large index number in common, other interfaces on the same device with more sensible index values still work and get graphed properly.
For the time being we have had to create the datasources, then disable them in cacti, and run our own external poller so that we can graph the interfaces until we find the reason why the cactid poller is returning bad values.
[size=117][i][b]Tony Roman[/b][/i][/size]
[size=84][i]Experience is what causes a person to make new mistakes instead of old ones.[/i][/size]
[size=84][i]There are only 3 way to complete a project: Good, Fast or Cheap, pick two.[/i][/size]
[size=84][i]With age comes wisdom, what you choose to do with it determines whether or not you are wise.[/i][/size]
[size=117][i][b]Tony Roman[/b][/i][/size]
[size=84][i]Experience is what causes a person to make new mistakes instead of old ones.[/i][/size]
[size=84][i]There are only 3 way to complete a project: Good, Fast or Cheap, pick two.[/i][/size]
[size=84][i]With age comes wisdom, what you choose to do with it determines whether or not you are wise.[/i][/size]
Also, what version of php are you running and do you have php-snmp support enabled?
What version of net-snmp do you have installed?
[size=117][i][b]Tony Roman[/b][/i][/size]
[size=84][i]Experience is what causes a person to make new mistakes instead of old ones.[/i][/size]
[size=84][i]There are only 3 way to complete a project: Good, Fast or Cheap, pick two.[/i][/size]
[size=84][i]With age comes wisdom, what you choose to do with it determines whether or not you are wise.[/i][/size]
rony wrote:Do you see that number in your poller cache?
Yeah, the poller cache entry is correct .... from memory anyway, I will have another go and look in the poller cache to make sure, but i'm pretty sure it was correct.