Switching from SNMP v2c to SNMP v1 has the effect, OpenNMS will use get requests with one (1) variables per request. It you use SNMP v2c by default bulk requests with 10 variables per PDU to reduce communication overhead and be more efficient. If you try to verify if the Mikrotik SNMP agent can deal with SNMP v2c you can use the snmpbulkwalk or snmpbulkget CLI tool to simulate a similar behavior than OpenNMS. The number of variables OpenNMS requests from a device can be configured per IP address with the "Configure SNMP by IP" and the "max vars per PDU" setting.
Listen to me...configure opennms to use v1 and you're done! Also if you use storeByGroup=true remove Octet String from collection.
All the best!
pavelgloba NA May 3, 2016 at 3:39 AM
Mikrotik works fine with all another nms'es
Antonio Russo May 3, 2016 at 1:55 AM
I was able to run the collection in opennms 16.0.4 using snmp v1. This is a workaround sure. you can also try to upgrade Router OS software. The probem is also related to Mikrotik Snmp Agent not conform to SNMP version2.
pavelgloba NA May 2, 2016 at 6:04 PM
Closing issue with words "use snmp v1" is not the fixing of a problem.
http://forum.mikrotik.com/viewtopic.php?f=2&t=72533 it was about a year ago. Opennms doesn't work properly with mikrotik devices.
Screenshots for rb751g-2hnd:
http://i.gyazo.com/9612ed9b096a46861fd2c4bc574b9a74.png
http://i.gyazo.com/c45953aaf1eb9b13d2ed5476087f1d16.png
Screenshots for Router OS x86:
http://i.gyazo.com/3a6cfa66a9ca008b646ef6761b637997.png
http://i.gyazo.com/44d8de048fefe2ff865c64c2e3a5197d.png
Is there a chance to fix it somehow?