- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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 ?
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You'll need to open a support case fo this bug - but it could take a VERY long time to get fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you checked the librenms documentation?
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You'll need to open a support case fo this bug - but it could take a VERY long time to get fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since removing an erroneous sign in a string is apparently a >6 months task for Cisco, LibreNMS has been patched to resolve this issue:
