Hello, I have this problem in the graphics of the interface consumption
When the consumption of an interface exceeds 3.4Gbps, the graph shows the consumption erroneously. I suppose the decimal point moves.
In reality the interface does not go down, it exceeds 3.4gbps, but in the graph it registers Mbps instead of Gbps.
DuDe can graph more than 3.4Gbps in the consumption graphs?
Thank you
+1
Eu também tenho o mesmo problema.
+1 Same problem here. Using version 6.43.16.
Your version is very old, time to update…
But that will not solve this problem. It is a known problem, it can only be worked around by selecting a smaller poll interval.
Thanks for your reply. I will try lowing the time.
Do you know if Dude should support 64bit counters for SNMP or are we still waiting for it?
Regards.
It does not support it for SNMP but it should support it for RouterOS API in current version.
Yes, the RouterOS seems to perform really well, but graphs for non RouterOS devices are completely useless.
Do you have the admin login for RouterOS devices (or another username you have added) configured, in addition to SNMP?
Yes, RouterOS devices have the username and password configured. They work perfectly. Only the non RouterOS devices are having strange behavior.
Ok I misread that…
You need to make sure that the polling interval is such that you cannot have more than 2^32 bytes of traffic in that interval.
The actual interval you need is depending on the maximal speed of your link.
Thanks. I’ve changed the interval to 10s and seems to be fine. I just realized once again that the dude is not serious. I’ts ok for home monitoring but not for large networks neither for big traffic. As usual, mikrotik has good ideas but poor realization. so sad, i think they will never stop disapoiting me.
I also abandoned the Dude after some evaluation.
It is too cumbersome to get it configured in a large network and I don’t want to risk losing all my config work due to e.g. a corrupt database and no documentation on how to repair it.
I’m actually planning to move to NetXMS, looks good to me. What NMS are you using now?