I’m impressed! The Dude is very good. I have installed it and was monitoring a network with 20 (or so) ROS boxes within a few hours.
One thing I have seen though, The Dude can not read SNMP (mib) from older RouterOS versions (I think 2.8.19 and down.)
After some playing I discovered that when you perform a SMNP walk on the older ROS’s the walk starts with a OID that is not the “object id” but a octet string (1.3.6.1.2.1.1.1.0) value “router”. Does this explain why older ROS’es are not recognized by SNMP?
Is it possible to make a new “Probe” that does recognize the older ROS mib?
After some playing I discovered that when you perform a SMNP walk on the older
ROS’s the walk starts with a OID that is not the “object id” but a octet
string (1.3.6.1.2.1.1.1.0) value “router”. Does this explain why older ROS’es
are not recognized by SNMP?
no, it is becouse of changes in Mikrotik enterprise MIB. As you can see for
yourself mikrotik probe is polling OID 1.3.6.1.4.1.14988.1.1.4.4.0 that
should be nonempty string. Older versions of ROS did not have this OID that
contains software ID.
Is it possible to make a new “Probe” that does recognize the older ROS mib?
Yes, you can choose to poll any other OID that is from Mikrotik MIB - e. g.
that starts with 1.3.6.1.4.1.14988 to use in identifying service.
Yes, you can choose to poll any other OID that is from Mikrotik MIB - e. g. that starts with 1.3.6.1.4.1.14988 to use in identifying service.
I see, this is working, thank you.
Is this also the way to get The Dude to recognize the interfaces under SNMP? I have added a pretty big numer of ROS configs now and on a lot of them I can not see the interfaces under snmp. These configs are all older as 2.8.20.
Are you also planning a branding package for The Dude? This would be a nice internet service for my clients.