Monitoring bandwidth usage on L-Com AP's

A quick search that I did did not reveal any MIB ready for download but what you might want to try to see if SNMP is enabled and if so, what OIDs are available is to do a walk on the device with the OID 1.3.6.1 with the v5 of the SNMP Tester

Thanks for the reply.

I finally got a chance to do the 'walk' test and I do find the OIDs that return the cumulative bandwidth figures.

For others who may be seeking this same info, here are the OIDs:

1.3.6.1.4.1.1567.1523.20.1.1.0 1.3.6.1.4.1.1567.1523.20.1.2.0 1.3.6.1.4.1.1567.1523.20.1.3.0 1.3.6.1.4.1.1567.1523.20.1.4.0 1.3.6.1.4.1.1567.1523.20.1.5.0 1.3.6.1.4.1.1567.1523.20.1.6.0 1.3.6.1.4.1.1567.1523.20.1.7.0 1.3.6.1.4.1.1567.1523.20.1.8.0 1.3.6.1.4.1.1567.1523.20.1.9.0 1.3.6.1.4.1.1567.1523.20.1.10.0 1.3.6.1.4.1.1567.1523.20.2.1.0 1.3.6.1.4.1.1567.1523.20.2.2.0 1.3.6.1.4.1.1567.1523.20.2.3.0 1.3.6.1.4.1.1567.1523.20.2.4.0 1.3.6.1.4.1.1567.1523.20.3.1.0 1.3.6.1.4.1.1567.1523.20.3.2.0 1.3.6.1.4.1.1567.1523.20.3.3.0 1.3.6.1.4.1.1567.1523.20.3.4.0

For my purposes, 1.3.6.1.4.1.1567.1523.20.2.3.0 1.3.6.1.4.1.1567.1523.20.2.4.0 show cumulative 'Received' and 'Transmitted' bytes, respectively, on the Ethernet1 port.

The OIDs, shown above, ending in 1.3.0 and 1.4.0 show the same info for the wireless port.

Since these are cumulative, I need to find a way to calculate the difference between each polling and then display the data in a graph.

G-Jim c):{-

You should be able to do this by using a Sensor Factory sensor where you can do calculations on multiple channels and display that info in a graph.

Sensor Factory Sensor

Again, thanks for the reply.

I created two custom sensors, implementing the 'delta' function. These gave me exactly what I was looking for. I then created a third sensor that combines the two into one graph.

G-Jim c):{-

Excellent! Thanks for sharing the information!

The graphing is working, but the wrong data is being displayed.

When I 'walk' 1.3.6.1.4.1.1567.1523.20 the 2.3.0 portion returns only the new cumulative total for band-width.

Within the Network Monitor, data returned from 1.3.6.1.4.1.1567.1523.20.2.3.0 also includes a speed component, and that is the data that is being displayed.

See screen shot: http://www.wyomerc.com/images/misc/ScreenShot1.jpg (Although label shows Megabytes, the data is actually in bytes).

It's the column labeled 'Value (speed)' that is being graphed, whereas I want the 'Value (volume)' data. How can I display the volume column?

G-Jim c):{-

You should be able to click on that channel's settings button in the sensor's overview tab and there you should see an option to show that channel in the charts.

I'm only seeing 'Value (Megabytes/s)' and 'Downtime' as channel options.

See screen-shot: http://www.wyomerc.com/images/misc/PRTGScreenShot2.jpg

Sorry for not reading that all the way through, I didn't notice you were trying to graph volume. Below is an article that explains why PRTG does not graph the volume.

https://www.paessler.com/knowledgebase/en/topic/13873-charting-volume-data

It boils down that if you were to try and graph the volume, it may look like the volume over the time is different than it is because of the way the data is read from SNMP. If you had a shorter scanning interval or longer scanning interval but the same speed, the volume would be different and would look quite odd in the graph leading you to believe that for that short or long interval, the speed was different.

I understand the reasoning, to a point. I still get spikes, in the graph, due to the fact that these devices reset the cumulative byte counters once they get a bit over 2GB. I can explain the spikes to those who would view these graphs - I will adjust the y-axis maximum to contain the accurate info, the spikes will appear as an occasional anomaly.

Thanks for all the info that you have provide.

G-Jim c):{-

Glad to help and you may also want to look into the options that are available for filtering spikes in graphs here:

https://www.paessler.com/blog/2013/04/02/prtg/how-to-filter-spikes-from-graphs-in-prtg