Hi Daniel, "I might be missing something obvious, but 14988 and 41112 don?t look like the same number to me?"
Oops, I grabbed the wrong configuration file as the redacted example. Ubiquiti (4112) equipment initially used a wireless MIB from MikroTik (14988), which is confusing. As a result I support multiple versions of this gauge to support different OIDs depending on firmware (it's more fun that it sounds). I did check which version was in use, and tested them all. The OID that returns a value via SNMP, consistently graphs a value of zero within MRTG. I added versions of the gauge with 'WaLK0.' & 'WaLK' prefixed to the OID, and those don't graph anything other than zero as well. I'm still trying to figure out precisely what changed in the output that prevents MRTG from parsing it, but I need a little direction on where to look. Thanks for the quick response, I appreciate it! Sincerely, Edwin A Epstein, III Rhinobee Internet Services ----- Original Message ----- From: "mrtg-request" <[email protected]> To: "mrtg" <[email protected]> Sent: Tuesday, July 12, 2016 5:53:10 PM Subject: mrtg Digest, Vol 112, Issue 25 Send mrtg mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.oetiker.ch/cgi-bin/listinfo/mrtg or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of mrtg digest..." Today's Topics: 1. Installation problem (thomaz portella) 2. Installation problem (thomaz portella) 3. Broken gauge seemingly without cause (Edwin A. Epstein III) 4. Re: Broken gauge seemingly without cause (McDonald, Daniel (Dan)) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Jul 2016 19:43:28 -0300 From: thomaz portella <[email protected]> To: [email protected] Subject: [mrtg] Installation problem Message-ID: <CAEd1yBOg7Sh2ZTVmBAhLiWB0=wk6bkom8+c+44hzgdiltad...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" I need to install GD, but the boutell site says it was replaced by libgd. I downloaded and tried to install, but the mrtg installation script doesn't recognize the libgd. What I have to do ? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.oetiker.ch/pipermail/mrtg/attachments/20160712/ca2656aa/attachment-0001.html> ------------------------------ Message: 2 Date: Tue, 12 Jul 2016 20:01:14 -0300 From: thomaz portella <[email protected]> To: [email protected] Subject: [mrtg] Installation problem Message-ID: <caed1ybpzev7w3v0v7cbvjsjx9yc-nf6s4vitrhoj3ek6nar...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" > I need to install GD, but the boutell site says it was replaced by libgd. > I downloaded and tried to install, but the mrtg installation script doesn't recognize the libgd. > What I have to do ? > Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.oetiker.ch/pipermail/mrtg/attachments/20160712/6f7f4534/attachment-0001.html> ------------------------------ Message: 3 Date: Wed, 13 Jul 2016 00:32:08 +0000 (UTC) From: "Edwin A. Epstein III" <[email protected]> To: mrtg <[email protected]> Subject: [mrtg] Broken gauge seemingly without cause Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hello, I've been using MRTG to graph the number of stations connected to various Ubiquiti access points. This was working quite well with no issues till apparently a new firmware broke MRTG functionality in some way that I can't identify. The working configuration: "Target[192.168.1.1_stcount]: CnTWaLK1. 3.6.1.4.1.14988.1.1.1 .2.1.3&CnTWaLK1. 3.6.1.4.1.14988.1.1.1 .2.1.3:[email protected] +0 WithPeak[192.168.1.1_stcount]: ymw SetEnv[192.168.1.1_stcount]: MRTG_INT_IP="192.168.1.1" MRTG_INT_DESCR="stcount" Options[192.168.1.1_stcount]: gauge,growright,nopercent,noi Title[192.168.1.1_stcount]: The-Broken-Gauge MaxBytes[192.168.1.1_stcount]: 256 XSize[192.168.1.1_stcount]: 600 YTics[192.168.1.1_stcount]: 1 YLegend[192.168.1.1_stcount]: Station Count Legend2[192.168.1.1_stcount]: stcount LegendO[192.168.1.1_stcount]:   stcount ShortLegend[192.168.1.1_stcount]: STc PageTop[192.168.1.1_stcount]: <h1>192.168.1.1 (stcount)</h1> <div id="sysdetails"><table> <tr><td>Nagios Name:</td><td>The-Broken-Gauge</td></tr> <tr><td>IP Address:</td><td>192.168.1.1</td></tr> <tr><td>Make & Model:</td><td>(NSM5) Ubiquiti Networks NanoStation M5</td></tr> <tr><td>MRTG Database ID:</td><td>548966</td></tr> <tr><td>MRTG Server:</td><td>Node 45 (10.10.3.3 )</td></tr> <tr><td>Maintainer:</td><td> [email protected] </td></tr> <tr><td>Gauge Type:</td><td>stcount</td></tr> <tr><td>Gauge Name:</td><td>Station Count Graph</td></tr> </table></div>" I'm aware (I think), that MRTG and snmpwalk use different libraries to manage the traffic. Hence, WaLK on a target line allows me to graph values otherwise unreadable/unreachable. This is the case with much of Ubiquiti equipment that is using a MIB from MikroTik (The OID above). I have two different versions of this gauge that support the two different MIBs that Ubiquiti uses, so I'm quite confident about my OIDs being correct. On the gauges that have issues a value of 0 is always received and graphed from the count walk. However, performing a snmpwalk still shows: "SNMPv2-SMI::enterprises. 41112.1.4.5.1.5.1 = INTEGER: -58" A count walk should return a value of 1, but never does. I can't see that anything has changed in the configuration file, or even the output from snmpwalk. I'm at a loss on how to proceed diagnostically here and would like some assistance in debugging MRTG and/or logging better information to find a fix here. Everything seems like it should be working as normal.... Sincerely, Edwin A Epstein, III Rhinobee Internet Services -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.oetiker.ch/pipermail/mrtg/attachments/20160713/1a286dc6/attachment-0001.html> ------------------------------ Message: 4 Date: Wed, 13 Jul 2016 00:52:55 +0000 From: "McDonald, Daniel (Dan)" <[email protected]> To: mrtg <[email protected]> Subject: Re: [mrtg] Broken gauge seemingly without cause Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" I might be missing something obvious, but 14988 and 41112 don?t look like the same number to me? From: mrtg <[email protected]> on behalf of "Edwin A. Epstein III" <[email protected]> Reply-To: "Edwin A. Epstein III" <[email protected]> Date: Tuesday, July 12, 2016 at 5:32 PM To: "[email protected]" <[email protected]> Subject: [mrtg] Broken gauge seemingly without cause Hello, I've been using MRTG to graph the number of stations connected to various Ubiquiti access points. This was working quite well with no issues till apparently a new firmware broke MRTG functionality in some way that I can't identify. The working configuration: "Target[192.168.1.1_stcount]: CnTWaLK1.3.6.1.4.1.14988.1.1.1<callto:3.6.1.4.1.14988.1.1.1>.2.1.3&CnTWaLK1.3.6.1.4.1.14988.1.1.1<callto:3.6.1.4.1.14988.1.1.1>.2.1.3:[email protected] +0 "SNMPv2-SMI::enterprises.41112.1.4.5.1.5.1<callto:41112.1.4.5.1.5.1> = INTEGER: -58" -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.oetiker.ch/pipermail/mrtg/attachments/20160713/96cee634/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg ------------------------------ End of mrtg Digest, Vol 112, Issue 25 ************************************* (null) _______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
