Dude 3.6 will not connect to RouterOS 5.x via SNMP.
Upgrading to Dude v4.0beta3 resolved the problem.
Dude doesn’t care about RouterOS version because it can monitor any SNMP compatible device, not just MikroTik routers.
weird… cause v3.6 wouldn’t read the SNMP values off of any devices I had running ROS 5.x. I upgraded to the beta version of dude and it seemed to fix it.. Maybe I just needed to restart the dude service… either way its working now so I’m happy.
We monitor a large number of 5.0 devices without issue
I monitor over 150 devies with dude V3.6 running and ALL routerOS V 5 snmp breaks after 7 days or so. Restart the server and all is good then.
Hi!
Your Dude server is an X86 or Routerboard? Because my Dude server is X86 and I have this problem…
Hello all,
I am having a similar problem. I was using The dude v4.0beta3 and I had some problems with “invalid OiD” in most of the SNMP communications even getting all the information I need throw SNMP Walk. So I decided to test the v3.6 of The Dude and it is now working fine for most of the devices but, in RoS v5.x I can’t see the RouterOS version or event Interfaces under RouterOS tab of the device (throw SNMP I can read everything now).
Just to ilustrate I am sending this image:
Uploaded with ImageShack.us
Is there anything I can do besides upgrade Dude?
Att,
Nataniel Klug
Have a x86 with RouterOS and dude installed .. Have the same issue with 4.0Beta3.
Make a virtual machine, and install on it the Dude. If the Dude crashed, then reboot the virtual machine. It’s around 10 sec and it is independent from the phisical router…
It is not the best, but better than nothing
I have already installed x86 machine the beta3. Dude stop the snmp monitoring the 5.XX version ros device. Working about ten days fine and stop the snmp. But the interesting way 4.xx version ros device working fine not stop the snmp protocol. Restart the dude server working again fine and can monitoring 5.xx devices.
The dude monitoring 500 ros devices,cisco,motorola,saf radios etc..