We have some questions on performance monitoring for the ePMP3000. We use PRTG for our network monitoring and have a mix of both ePMP2000 and ePMP3000 in our network with everything running 4.4.3 firmware.
ePMP2000
dlwlan total used frame time per second - worked well and was a good data point to know when the AP was getting overloaded. It would display a percent and was easy to understand. The same MIB with ePMP3000 shows a value per second such as 2,281/second. If we don’t know a maximum value how can this number be used?
Brian Chan of Cambium suggested using dlwlan total available frame time per second. So for the ePMP3000 this shows a value of 3,549/second and again how are we to use this number without knowing a maximum values? For the ePMP2000 it is showing 731,989/second but how could the ePMP2000 have orders of magnitude more available frame time than the ePMP3000?
What are the best Cambium MIBs to use to measure ePMP2000/ePMP3000 performance to know when the AP is overloaded?
Actually, to monitor Frame Utilization in Downlink I would recommend to use the following OID that represents 10x Value displayed on UI and relevant both for ePMP2000 and ePMP3000:
snmpget -v 2c -c private localhost 1.3.6.1.4.1.17713.21.2.1.113.0
dlWLanTotalAvailableFrameTimePercentage OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Aggregated downlink frame 10X percentage time
Range = [1..1000] 0.1% = 1; 100% = 1000
Device Allocation: AP"
Thank you for the information. We had actually tried that OID but it was returning values like 737%. Thank you for your explanation about the OID returning 10x value – this now makes sense. For the moment we will use this OID for performance monitoring. I suppose we will have to divide by 10 in order to get the correct value.
Another question if you have the time: Is there any way to change the value returned to a normal values and not 10x so the percent will display correctly?
It basically needs to return a whole number - not a fraction. So, the choice is to display 10x the actual value, and therefor has the 10ths precision. It’s usually possible to divide that by 10 in your graphing package and get the correct value, with the 10ths precision intact.