SNMP - AX88u

[Phantomski]

Write data with the InfluxDB API | InfluxDB OSS v1 Documentation

Use the command line interface (CLI) to write data into InfluxDB with the API.

docs.influxdata.com

Looks reasonably easy to use. Just need to delve into your code to figure out what values, tags etc. are needed, unless you have a reference already?

Do I sense one of our scripting gurus contemplating a solution? If yes, it's a massive thumbs up from me

 

[Markfree]

Just to add up.
I use a mini usb 3 flash drive in my RPi and it serves my monitoring tools like a charm; with a passive cooling case.
It is very discrete and much faster than an SDcard. No hick ups whatsoever.

As for the router, Zabbix Agent can collect basically any data and offloads it to the Server for processing. It doesn't even scratch system's load.

 

[xtv]

Besides the extremely interesting discussion regarding monitoring tools, I'd like to move back to the original question: anyone has an idea concerning how to have Net-SNMP (not mini-snmpd) running on the router?
Or why exactly snmpd causes a kernel crash?
I mean I'd expect a process crash, but not a kernel crash; a kernel crash is a symptom that there are unmanaged cases somewhere in the kernel source.

 

[RMerlin]

snmpd pokes around into Kernel structures, like the proprietary Broadcom network switch. Who knows if it`s a bug or a compatibility issues within those closed source driver - out of my control.

 

[xtv]

snmpd pokes around into Kernel structures, like the proprietary Broadcom network switch. Who knows if it`s a bug or a compatibility issues within those closed source driver - out of my control.

Thanks for the reply and most of all thanks for the great work

 

[Ari_el]

Anybody noticed issues lately with mini-snmpd on AX88U? interface counters seem to be gone (there is no interface table at all when doing an snmpwalk) and it seems to be ignoring community string configuration etc.


mini-snmpd --version
v1.6

The problems may have started when I updated entware packages a couple of months ago, and I didn't notice. Actually mini-snmpd 1.6 is supposed to support 64 bit interface counters which would have been nice

 

[xtv]

Anybody noticed issues lately with mini-snmpd on AX88U? interface counters seem to be gone (there is no interface table at all when doing an snmpwalk) and it seems to be ignoring community string configuration etc.


mini-snmpd --version
v1.6

The problems may have started when I updated entware packages a couple of months ago, and I didn't notice. Actually mini-snmpd 1.6 is supposed to support 64 bit interface counters which would have been nice

I just checked, for me mini-snmpd is still working regularly (and I'have the same version installed).

However, TBH, I've decided to walk a different monitoring path. Unfortunately mini_snmpd is way too much mini for AX88u (e.g.: I need to monitor 11 interfaces and mini_snmpd monitors at most 8 interfaces)

First I've been trying corgan's excellent monitoring script (which pumps data into an InfluxDB), but I've found that a deep stat collection is too resource hungry for my personal needs.

So at first, I've been trying to implement a quick of port corgan's script in Python, which improved performances a lot and reduced the load on cpu.

Finally I've decided to try to write a monitoring tool from scratch in golang to pump data into InfluxDB.. and I've decided to stay there.
The golang tool has almost zero load on the CPU (which for me is very important, since when I'm working remotely I want as much band as possible on the VPN tunnels - I've 300Mbps unload), eats just about 8MB of RAM (which on a 1GB switch is almost nothing) and does not rely on cron (which fills the logs with unnecessary information).

Yet it is still incomplete; I should polish the code, integrate a better logging mechanism to pump logs directly in syslog (ready to be sent to the remote log server without additional configuration) and to figure out an efficient way to get traffic data by local client
About the last point, I don't like very much the idea of altering the firewall just to gather data (which BTW also misses data regarding newly connected devices until iptables are updated), moreover the biggest point is that there is already a feature of the router to monitor client traffic, thus creating a separate mean to collect the same data would only use resources to do the same job some other process is already doing. The best would be able to pick the client traffic data from the same source used by the standard feature, but I still have to figure out from where traffic details are collected.

 

[Ari_el]

I just checked, for me mini-snmpd is still working regularly (and I'have the same version installed).

However, TBH, I've decided to walk a different monitoring path. Unfortunately mini_snmpd is way too much mini for AX88u (e.g.: I need to monitor 11 interfaces and mini_snmpd monitors at most 8 interfaces)

First I've been trying corgan's excellent monitoring script (which pumps data into an InfluxDB), but I've found that a deep stat collection is too resource hungry for my personal needs.

So at first, I've been trying to implement a quick of port corgan's script in Python, which improved performances a lot and reduced the load on cpu.

Finally I've decided to try to write a monitoring tool from scratch in golang to pump data into InfluxDB.. and I've decided to stay there.
The golang tool has almost zero load on the CPU (which for me is very important, since when I'm working remotely I want as much band as possible on the VPN tunnels - I've 300Mbps unload), eats just about 8MB of RAM (which on a 1GB switch is almost nothing) and does not rely on cron (which fills the logs with unnecessary information).

Yet it is still incomplete; I should polish the code, integrate a better logging mechanism to pump logs directly in syslog (ready to be sent to the remote log server without additional configuration) and to figure out an efficient way to get traffic data by local client
About the last point, I don't like very much the idea of altering the firewall just to gather data (which BTW also misses data regarding newly connected devices until iptables are updated), moreover the biggest point is that there is already a feature of the router to monitor client traffic, thus creating a separate mean to collect the same data would only use resources to do the same job some other process is already doing. The best would be able to pick the client traffic data from the same source used by the standard feature, but I still have to figure out from where traffic details are collected.

Thanks for the detailed response!
In the end I could confirm I was not the only one bitten by this problem, if you update mini-snmpd with the opkg package manager and get the current version, it will work but it will not expose any interface counter (new default). It wasn't difficult to get mini-snmpd to work again. It now includes 64-bit counters for interfaces which was a nice bonus, details here,

RT-AX88U snmpd - mini Guide

Using amtm today, I discover that Entware packages have been updated and we now have mini_snmpd - 1.6-3 listed via amtm. The new package trashes /opt/etc/init.d/S50mini_snmpd so I used the backup made previously. All appears to work, with the router log showing: mini-snmpd v1.6 starting...

www.snbforums.com