I've installed the snmpd package on my local Ubiquiti node, but can't seem to figure out where the configuration file, snmpd.conf should reside.
Any pointers would be appreciated!
73 - Orv - W6BI
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Check out this reference: http://wiki.openwrt.org/doc/howto/snmp.server
Looks to be "UCI" compatible, so look for a config file in /etc/config . I've not investigated this package myself, so I'll defer further to Conrad--he's investigated this before.
Joe AE6XE
Thanks, Joe - I'll check it out
Orv - W6BI
Joe is correct, it uses the UCI Config format, and is somewhat poorly documented at the moment on OpenWRT core.
This also may be of interest to you to comment, its the early stage of a concept for a MIB we are discussing implementing into a future build to provide more of the data (we think) users will need http://bloodhound.aredn.org/products/AREDN/wiki/develsandbox/SNMPMib
You may want to add a field for Grid Square for those people who do not wish to pinpoint their exact location via lat/long but give a general idea of where they are located. There are a number of programs/apps out there that handle grid squares and can give good directions to aim antennas and distance to another grid square. The weak-signal microwave crowd uses them all the time.
73, Mark, N2MH
OK, I can now poll my local Ubiquiti mesh node with snmpwalk and get data back.
I had hope to use Zenoss as the monitoring tool. Although that's way overkill, it's what we use and I am quite familiar with it. However the newest version (5.0) requires a minimum of 4 CPU cores and 20 (!) GB of RAM.
So I started looking for a suitable lightweight network monitoring app. I found monitorix and zabbix but both of them leave me cold.
Any other recommendations?
Thanks
Orv - W6BI
We'd likely want to offer a Window-based standard... broader audiance and all. Mikrotik offers the "The Dude". It's free and has a wireless slant. Offers map backgrounds, etc for network visualization. Unfortunately the MIBs are all written for their wireless routers, but we intend to write our own anyway.
Andre
Thanks, Andre. But that's no help to me - there are no Windows machines at my QTH.
I'll keep looking.
Orv
A simple snmp package that works for graphically displaying bandwidth usage is MRTG. it works in Linux and Windows. There is more that you can do with this.
I run it in Linux at home to monitor my Cisco gear. This includes routers and switches. I can see what my bandwidth utilization for the home equipment as well as what the BBHN network is doing. I haven't looked at the nodes on the BBHN yet. MRTG is easy to setup.
https://www.iceflatline.com/2009/08/how-to-install-and-configure-mrtg-on...
Mike AE4ML
Thanks for the tip, Mike! I'll check it out.
73 - Orv - W6BI
We got mrtg configured to watch two nodes tonight. Will be interesting to watch as the traffic grows.
Looking nice,
Will be curious to hear how it goes as you get more traffic.
One item, you may want to monitor wlan0 more than wlan0-1.
wlan0-1 is a 'monitor' interface, its keeping an eye on all RF traffic (its only used currently by the really by the not-so-well-polished wifiaimer application)
wlan0 has the real mesh traffic on it. Though I suppose wlan0-1 could be interesting for understanding some interference by other wifi traffic, I had never thought to monitor it with SNMP but that could be useful data for those who want to know what other wifi devices on the same channel/bandwidth combo are doing with RF packets.
Based on that comment, we took a look at the interfaces in our two test nodes:
According to the SNMP data, on the W6BI-TP-Link-REMOTE (TPLINK CPE210), this is the mapping of interface number to name that we see:
Interface Name
1 'lo'
2 'eth0'
3 'No Name'
4 'eth0.2'
5 'eth0.0'
6 'eth0.1'
7 'No Name'
8 'wlan0-1'
On W6BI-24-0 (Ubiquiti Bullet M2 HP), this is the mapping:
Interface Name
1 'lo'
2 'eth0'
3 'No Name'
4 'eth0.2'
5 'eth0.0'
6 'eth0.1'
7 'No Name'
8 'wlan0-1'
So, what's the correct wireless port for mesh?
It's likely #7. Not sure why it's reporting no name, might have a bug that needs to be reported (check to make sure wifi is actually coming up etc)
It'd be interesting to see what you get on eth0. It could be all traffic on the interface, including traffic with a 802.1q VLAN tag, or only untagged traffic. I would presume eth0.0 would give you untagged traffic, since 0 is a reserved VLAN ID.
I'd be happy to create a bug report - just need to know what to report :-/ "wlan0 port doesn't appear in list of ports"?
I was questioning is the node actually linking via RF? If it is than the concern is minimal and its some display item, if not there may be an issue (and that is what needs a bug report if an issue exists)
Of course there are several known TPLink issues in the beta so some could be connected as well.