Skip to main content

Hello,

using centreon_ubiquiti_airfiber_snmp.pl --plugin=network::ubiquiti::airfiber::snmp::plugin --mode list-radios will return UNKNOWN: Need to specify OIDs

According to tcpdump it sends snmp request:
GetNextRequest(33)  .1.3.6.1.4.1.41112.1.3.1.1.14

and gets response:
GetResponse(35)  .1.3.6.1.4.1.41112.1.4.1.1.1.1=5

and that is all. Tested on multiple devices with multiple firmwares with the same result. What is wrong?

Hello,

could you provide the model of your APs?

I know I use this plugin for a lot of ubiquity ap, not “airfiber” but various model (UAP-AC-Pro, U6-LR...) , the “list-radios” and “radios” does not work, but the load, memory, interfaces and list-interfaces mode is working.

I think AirFiber was a specific product, when I do a snmpwalk for the unify oid .1.3.6.1.4.1.41112

I can see my radio here in this table : .1.3.6.1.4.1.41112.1.6.1.2.1.6 plus various other stats

 

I can see the plugin for airfiber calling  .1.3.6.1.4.1.41112.1.3.1.1.14 wich is not present on my devices, (what you get with your tcpdump is the “snmp next”, which the first oid present after what you requested)

 

I googled and found airfiber access point usually with “AF” in the name, so I guess someone would need to develop a new plugin specific for Ubiquity AP non-airfiber

 

googling more, they are indeed different : 

mibs.observium.org/mib/UBNT-UniFi-MIB/

mibs.observium.org/mib/UBNT-AirFIBER-MIB/

 

well, based on  what I see on the forum from unifi the UnifiVapTable should contain everything, but the number of client (vapstation) is bugged between the web UI and what the snmp reports

anyway, this needs the development of a new plugin for unifi AccessPoint, it was just a fluke that the load/memory/interface were using the same oid on both model family

(if you do have airfiber model, then you could open a bug report on the github directly and you will be asked for snmp dump)

 


Hello,

it is AF60-LR, firmware GP.V2.6.2 (GP.ipq806x.v2.6.2.47073.221024.1706). I can see radio table under .1.3.6.1.4.1.41112.1.11. I will open a bug report on github, thanks.


Reply