I’m trying to figure out why MT devices don’t have a uniform oid database and if there is a way around it.
Example, 2 devices, a NetMetal 55HP Triple and a NetMetal 55HP have different oid’s for frequency. Both devices are setup as AP Bridge running the same software and same firmware. I can set them up identical to eachother but I still have 2 oids for frequency.
Why is this and how can I make them the same? It’s not just frequency, it’s many things I want to monitor, like ethernet status as well. And why can’t we have a power level oid without the mac address for PTP modes? This is making graphing not fun. We use hardware from nearly every manufacturer and MT is the only one that acts this way.
so you can use the terminal to get the OID information like: interface print oid but this will not be available everywhere, the other way you could do this is get a SNMP server with a ‘walk’ function.
The last option is to use a monitoring service that already has most of the OID’s included, if you look at librenms it has alot of the Mikrotik monitoring sorted for you without having to set much up other than IP connectivity to the device you want to monitor. https://www.librenms.org/
You can not make the same, the first part 1.3.6.1.4.1.14988.1.1.1.3.1.7
(iso.org.dod.internet.private.enterprises.mikrotik.mikrotikExperimentalModule.mtXRouterOs.mtxrWireless.mtxrWlApTable.mtxrWlApEntry.mtxrWlApFreq)
is the mtxrWlApFreq value, and the last number is the interface index.
Obviously different models have different interfaces and different interfaces order inside the hardware.