as per the title, all the links between the devices i have on my network have stopped displaying the bitrate at what is currently travllign through an interface like ether1, wlan1, etc etc
all my link state 0bps up and down, i am running windows server 2003 standard, this has only happened since upgrade from 3.1 to 3.4.
Yes, I am also having this problem. Links either show zeros or the bitrate stops updating. In the case of links displaying zeros, double-clicking the link and clicking “OK” on the Settings… screen seems to get them working again. If the bitrates stop updating, I have to go to Settings on the device the links are attached to and re-enter the password. Links immediately start displaying data rates again. This isn’t a good fix, though, since we’re missing out on the historical data (graphs, etc) for these links.
Dude 3.4
Links in question are all routeros mastering type.
I’m using a 2003 server with dude 3.2 and got lots of bit rate graphing problems here
Dude was working perfeclty until 1 week ago, than after a windows upgrade the problem begun. I dont
know if its just a coincidence or one of upgrades has affected Dude in some way.
When the problem occour, if you go Settings → snmp the monitored interface is not shown anymore. Sometimes
refreshing list or disable/enable snmp you can see interface and graphs are displayed again.
The problem is not with the Dude v3.4, this problem is on the RouterOS end. Was running fine with ROS v3.15 on all the devices. As soon as we upgrade that device to ROS v3.24 we loose our bitrate’s.
I am getting links change their snmp port number, showing the wrong data. It seems every port on one switch is wrong. I changed it and the next morning, same problem.
Any update on this guys, we are having the same prob, all good until upgrading our router to 3.25, it stopped working straight away
Using Dude 3.4 running on Windows 2K3 Std, a bit annoying…
Interesting thing though, when you open the settings page of the device the links start to show bitrates and they keep working whilst you have the device properties screen open.
That’s a bummer, I was going to upgrade tonight to see if 3.26 fixed the prob, I suppose as it’s not a real functional issue it’s not high priority, it’s just a pain in the neck.
I can confirm that without any changes to The Dude and downgrading a router which was having this problem to 3.22 the problem is fixed, it is definitely an ROS problem.
Incidentally, I have downgraded because there were just so many issues with 3.26 and 3.27, I just could not run in production.
This “bug” appears in all RouterOS version above 3.22. Versions 3.23 - 3.29 do not read the bitrate when using RouterOS mastering on the link, unless you keep the “settings” window open for that particular router. Once you close the settings window, the Dude will stop collecting the bitrate for the router.
The only other option is to downgrade to 3.22, and hope Mikrotik finds time to resolve this issue in an upcoming RouterOS release.
Hey Normis, whilst you’re on is there any chance you could confirm this is a known bug that is being worked on and that it is a RouterOS version issue rather than Dude version issue?
I really have no idea, we have some Dude installs where bitrates are showing fine in v3.4. What kind of links are they? Double click on that label to see the source of this data, and verify that it’s still available (ie. there is no problem in SNMP).
SNMP has no problems. It is when you use RouterOS to get the bit rates. For me it seems to happen when Dude looses connectivity with the router that is supplying the statistics for a length of time. I guess the Dude creates a TCP session with the router but when it looses connectivity it only retries a few times before it gives up?