[ZBXNEXT-5540] MikroTik WiFi monitoring template Created: 2019 Nov 01  Updated: 2024 Apr 10  Resolved: 2020 Aug 31

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Templates (T)
Affects Version/s: None
Fix Version/s: 5.0.4rc1, 5.2.0alpha2, 5.2 (plan)

Type: Change Request Priority: Minor
Reporter: Vitaly Zhuravlev Assignee: Maxim Chudinov (Inactive)
Resolution: Fixed Votes: 1
Labels: Template_Net_Mikrotik_SNMPv2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team INT
Sprint: Sprint 66 (Jul 2020), Sprint 67 (Aug 2020)
Story Points: 3

 Description   

Please extend mikrotik template to monitor wireless AP cases.

  • Design generic Wireless AP monitoring model
    • Metrics to gather
    • Triggers to control if any
  • Implement it on mikrotik for (Indoor AP)


 Comments   
Comment by dimir [ 2020 Aug 20 ]

Some Q/A with tech support from MikroTik:

1. General question, as I understand not all available SNMP OIDs are currently in recent Mikrotik MIB file, so it's better to use the OIDs directly (not MIB-MIKROTIK::xyz), when performing SNMP queries?

The latest MIB file is here, it is from 2019/12;
https://wiki.mikrotik.com/wiki/Manual:SNMP#Management_information_base_.28MIB.29
In case you can find any new OID, that is not there, let us know about it.

2. Regarding access point monitoring, is the correct way to see which OIDs are available:
[user@admin] > /interface wireless pr oid

/interface wireless print oid, oids are used for clients (mode=station), for AP we suggest using /interface wireless registration-table print oid

<dimir> So instead of checking how APs are doing one can monitor active connections.

3. Could you describe the following OIDs:
MIKROTIK-MIB::mtxrBoardName
MIKROTIK-MIB::mtxrWlCMState
MIKROTIK-MIB::mtxrWlCMRegClientCount
MIKROTIK-MIB::mtxrWlCMAuthClientCount
MIKROTIK-MIB::mtxrWlCMChannel

BoardName - RouterBOARD name (all RouterBOARD names are there)
WlCMState - Wireless interface state
ClientCount - number of clients going through authentication procedures + number of clients established connection
AuthClientCount - number of authenticated clients established connection
RegClientCount - number of clients going through authentication procedures

4. We saw some strange behaviour that when no client is connected to the AP its "mtxrWlCMState" is reported as down. Is that true, and if yes, is there other OID that should be used to monitor the AP "state"?

Yes, on MikroTik RouterOS when no clients are connected, device state is reported as down/inactive. That is the question, what is considered to be down, as you may setup alerts when registration-table has no clients connected at the moment.

5. The "ssid" OID 1.3.6.1.4.1.14988.1.1.1.3.1.4.X is the correct one to use to get the name of the AP?

Yes, it colud be used to check SSID on station.

6. On my device the wireless interfaces return type (ifType OID) is 71, could there be other possible types of wireless interfaces? Basically, we need the list of types that could act like access points to filter others out.

Yes, all wireless interfaces are returned with ieee80211, as MikroTik RouterOS supports only this standard.

7. Perhaps you have an idea what other metrics are usually MikroTik users (admins) interested in (except standard things like interface in/out traffic) e. g. radio signal strength etc.?

As you have specified at the beginning, that you want to make universal template (that is not very easy topic), as we have tried to make similar templates from time to time.
As for wireless, mostly parameters from registration table + number of connected clients to interface (however keep in mind that there could Wireless Manager CAPsMAN used, then parameters will ve different).

8. Is there, and if yes, which OID could tell if the AP is controller based or not?

At the moment there is no option for that, but we will try to add it in the upcoming versions.

Comment by Maxim Chudinov (Inactive) [ 2020 Aug 26 ]

Available in:

Generated at Thu May 15 06:03:45 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.