Hi,

I noticed my snmp monitoring (LibreNMS) is missing wireless metrics like client count, etc. since I replaced a hAP ac2 with a hAP ax2 running routerOS 7.7beta4 and wifiwave2 package.

hAP ac2 7.7beta4

hAP ax2 7.7beta4
On hAP ac2 I can print OIDs using which doesn't exist on the wifiwave2 menu!

Is this possible right now?

Thanks a lot and best regards!

Same thing...wondering why it was removed.

/interface print oid

works.

Yes it works, but it lacks all Wireless related metrics, which were available before.

I would like to jump on this train. Was bummed to find out that the wifiwave2 package doesn't support SNMP (so it appears hap ax2/ax3 and possibly other AX devices).

Has anyone contacted support? Any way to put this in as a request?

Feel free to do so ...

Has anyone contacted support? Any way to put this in as a request?

I noticed this too, but didn't do anything. AFAIK, there just the standard MIB-2 interface stats (e.g. the ones shown /interface/print oid). Maybe wifiwave2 stuff is hidden somewhere... but in latest Mikrotik MIB, "mtxrWireless" doesn't have any for wifiwave2 & couldn't find anything wifiwave2 related in MIB.

FWIW, the stats are pretty slim in wifiwave2 generally, so doubt SNMP would exceed what you see in winbox/CLI, nor likely be same OID as "old wireless" ones... but dunno.

I'd recommend you file a ticket at: http://help.mikrotik.com

Just found this, I'm bummed as well. My Grafana dashboards went one by one away

Did anyone file a support request?

Just found this, I'm bummed as well. My Grafana dashboards went one by one away

Did anyone file a support request?

I did. Got this for a reply

Hello,

Thank you for contacting MikroTik Support.

We are aware of this issue and are looking to fix it in upcoming RouterOS versions.

Best regards,

Matīss O.

Still limping along, and doing an snmpwalk of the device breaks out fairly quick with an oid increment error.

Just found this, I'm bummed as well. My Grafana dashboards went one by one away

Did anyone file a support request?

I did. Got this for a reply

Hello,

Thank you for contacting MikroTik Support.

We are aware of this issue and are looking to fix it in upcoming RouterOS versions.

Best regards,

Matīss O.

Still limping along, and doing an snmpwalk of the device breaks out fairly quick with an oid increment error.

Cool, thanks for the fast reply. OK, I can survive for a couple of releases if they do end up fixing it. But the graphs were indeed nice and useful. Lose one (snmp) win one (wpa3), that's life

Just landed in this post looking for the new capsman connected clients oid

Did you find the new OIDs are implemented?

Regards

You really should ask support.
Support@mikrotik.com

Thanks, I've open a ticket to support

Thanks, I've open a ticket to support

Are there any good news on this topic? I really miss these options...

We are in the same situation, we have to provide statistics to upper management, and the number of "users" is quite important for us. We are now using the following workaround in our SNMP monitoring tool:

• from the interface ifindex, get the number of the instance in the bridge MIB, walking 1.3.6.1.2.1.17.1.4.1.2 until the ifindex is found

• count the entries in the mac table, interface column at 1.3.6.1.2.1.17.4.3.1.2 having that instance number in the value

This way we do not count the associated clients, but the different MAC addresses that in the FDB are seen on that interface. For the counter of all the clients, we simply sum over the wifi interfaces.

Of course it is not the same thing but it is a workaround. Not all SNMP monitoring tools can do this indirection.

I really hope this feature is re-added soon, it seems to me just a matter of mapping in SNMP a value that is already available somewhere.

Hi All,

Does anybody have any (good) news regarding this issue?
I have the same issue with my ac^3, all wireless interface statistics are gone.
But not all my devies are affected by this, for example hAP lite is working fine.

I think (suspect) only the newer devies have this bug, which are using "wifi-qcom-ac" package.

Thanks,
Janos Vincze