MR28 wrong SNMP string sysDescr

Solved
braham2019
Here to help

MR28 wrong SNMP string sysDescr

I use LibreNMS for SNMP. All of my AP show up correctly and are recognized by LibreNMS.

.1.3.6.1.2.1.1.1.0 = STRING: Meraki MR76 Cloud Managed AP

However, the MR28 has a "wrong" string (the "=" is shown in the name), so that LibreNMS does not recognize this as a Meraki AP.

.1.3.6.1.2.1.1.1.0 = STRING: =Meraki MR28 Cloud Managed AP

Is there a way to override this ?

 

1 Accepted Solution
PhilipDAth
Kind of a big deal
Kind of a big deal

You'll need to open a support case fo this bug - but it could take a VERY long time to get fixed.

View solution in original post

4 Replies 4
alemabrahao
Kind of a big deal
Kind of a big deal

Have you checked the librenms documentation?

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

The problem is clearly with the Meraki AP having incorrect SNMP settings. See below

snmpwalk -v 2c -c public 192.168.0.200 iso.3.6.1.2.1.1.1.0
iso.3.6.1.2.1.1.1.0 = STRING: "=Meraki MR28 Cloud Managed AP"

snmpwalk -v 2c -c public 192.168.0.155 iso.3.6.1.2.1.1.1.0
iso.3.6.1.2.1.1.1.0 = STRING: "Meraki MR33 Cloud Managed AP"

snmpwalk -v 2c -c public 192.168.0.160 iso.3.6.1.2.1.1.1.0
iso.3.6.1.2.1.1.1.0 = STRING: "Meraki MR76 Cloud Managed AP"

snmpwalk -v 2c -c public 192.168.0.167 iso.3.6.1.2.1.1.1.0
iso.3.6.1.2.1.1.1.0 = STRING: "Meraki MR33 Cloud Managed AP"

 

PhilipDAth
Kind of a big deal
Kind of a big deal

You'll need to open a support case fo this bug - but it could take a VERY long time to get fixed.

After some back and forth with support and providing the necessary proof of the difference in OID string in comparison to other MR AP, I got the reply "I have reported this issue to our development team and they are looking into resolving it. I will keep your posted once a fix is released. "

Let's see when that happens...

Get notified when there are additional replies to this discussion.