Bongo is a tool for gathering statistics on a large number of Canopy SMs with minimal configuration.
You give Bongo a list of LUID IP subnets (see AP IP Configuration below for setup instructions) and it will send SNMP queries to every possible IP in those subnets and records the responses. Responses are recorded in Round Robin Database files (RRD). There is one RRD file per MAC address. Because Bongo identifies and stores data in a database keyed by MAC address you can follow a SM even if it shifts to a different LUID IP.

Why not set a static management IP on every SM and add it to a existing tool such as Cacti? I wanted something that would work with zero configuration on the SM and management server.
With Bongo you can install a SM and stats are automatically recorded for the SM. No messing with static management IPs or other post-install configuration.

I’m currently using Bongo to poll a segment of my network with around 1,500 SMs every five minutes. The big thing to watch performance wise is disk IO.
Do NOT use Bongo with APs running SW 7.3.6 or older. The LUID IP routing code in that software train has a bug that will crash the IP stack on the AP if you attempt to poll a LUID IP that is (128, 64, I don’t remember exactly, just that it was a power of 2) higher than the highest LUID registered.

Configuration settings go in the config.yaml file. It should be self explanatory. If you have any questions or feedback please send me a email: jda@tapodi.net.

Requirements

Bongo requires perl 5.8+ and the following CPAN modules:

• YAML
• SNMP::Effective
• RRD::Simple
• NetAddr::IP
• File::Path
• Time::Duration
• Data::Dumper

Download

Releases

• Bongo 1.0

Development

Clone the source repository with Mercurial:

hg clone http://bitbucket.org/jda/bongo/

Or check out changes at bitbucket.

AP IP Configuration

You will need one RFC1918 /24 subnet per AP.
Lets say you pick 10.0.40.0/24 and the AP's LAN1 IP address is 172.16.40.4 with a gateway of 172.16.40.1.
Set the AP's LAN2 IP address to 10.0.40.1.
On the router that is gateway for LAN1 (IE, on 172.16.40.1) static route 10.0.40.0/24 to 172.16.40.4.
Now every SM that registers to the AP will get a private management IP address of 10.0.40.X where X is the SM's LUID.