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.
gandalf wrote:Glad to hear this. So 087c would definitively be good for you
Fyi, I'm using Cacti 0.8.7d against a Peplink 300 device. I was unable to get Cacti to work against the Peplink using v3 or v2c. I tried setting the maximum number of OID to "1", but it didn't seem to help. It worked only when I enabled v1 SNMP on the Peplink and configured the same in Cacti. Using v3 and v2c, I was able to snmpwalk and snmpbulkwalk the Peplink using the same OID from the same machine running Cacti. So it would seem to have something to do with how Cacti is calling the routines or the underlying library that Cacti is using.
(I'm very new to Cacti, but can help debug if there's anything you'd like me to check.)
First, we need to know whether php-snmp or net-snmp is used. Please visit "System Utilities -> Technical Support" and post the line stating the SNMP Version.
Then, please tell us how your successful SNMP calls using V2/3 looked like (please erase passwords)
Reinhard
Cacti is installed on an older Fedora 6 system with a lot of mostly official updates. After setting things up in Cacti with same parameters and then doing a verbose query on the "SNMP - Interface Statistics" datasource, I see this output:
+ Running data query [1].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/projects/cacti/resource/snmp_queries/interface.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.2.1.2.2.1.1'
+ No SNMP data returned
+ Found data query XML file at '/projects/cacti/resource/snmp_queries/interface.xml'
+ Found data query XML file at '/projects/cacti/resource/snmp_queries/interface.xml'
+ Found data query XML file at '/projects/cacti/resource/snmp_queries/interface.xml'
I see the same output if I change the "Maximum OID's per Request" parameter from the default 10 to 0 or 1.
I'm now thinking that timeouts might be a factor, at least for v2. I was playing with different "Max OID's per Request" and it started working (per the "Get Verbose Results" response) in v2c randomly. I then increased my timeout setting (from 2000 to 10000) and the responses are working consistently now. At first I thought it was only when "Max OID's per Request" was "0" or "1", but I've since had successful results with "10". I think the Peplink is just slow in responding.
That was only for v2c though. I tried again using v3 with higher timeouts and still doesn't work. Whereas v2c would take a few seconds to respond even if it eventually came back with no results, v3 returns immediately.
Note...I'm not sure this is worth spending time on unless you think it could help uncover some other potential issues with Cacti.
snmpwalk -u {myusername} -a MD5 -A {mypassphrase} -l authNoPriv -x DES -v3 {myip} .1.3.6.1.2.1.2.2.1.1
Lets discuss the V3 example first.
You are using -x DES but -l authNoPriv. What are the settings for that Host in cacti? To use authNoPriv, cacti requires Privacy Protocol set to [None]. In this case, "-x" will be skipped as well.
Reinhard
BTB:
You may find different results when installing php-snmp, both in V3 and V2c cases. Please try and report results
