I recently upgraded one of my routers from version 3.3 to version 3.16. Now with 3.16 I noticed that the Tx and RX rates for interfaces are not displaying correctly in Winbox. For example, Winbox is showing 10.5 Mbps TX on my LAN interface but I know that there’s really about 30 Mbps on that interface. Also, the CPU usage in Winbox is showing 0% and I know that’s not correct.
The interesting thing is that I’m graphing this router with Cacti and Cacti is showing the correct stats. Is this a bug?
I know the real traffic amount based on the interface statistics on the devices on either side of my router.
I don’t have an concrete proof that the CPU is wrong, however, I find it highly unlikely that I’m using 0%
Torch is also showing the wrong stats…at least at the bottom where it adds up the total traffic. I haven’t had time to actually drill down a single stream to see if that’s correct or not.
Just a note on the “minimal speed gain”. With multi-cpu enabled, my CPU usage is about 7-10%. Once I turned it off, I now have 30-35% usage. This is with about 400 PPPoE sessions and about 20Mbps traffic usage. That is not a minimal impact!
do you realize that CPU usage doesn’t reflect SPEED, just available recources?
multi-core has not been stable yet, don’t use it if it causes problems. on certain systems it works well, but we are still working on it (actually, it more depends on Kernel developers).
normis, thank you for taking the time to reply to this topic. Response from Mikrotik support staff is very much appreciated. This tells us you are listening to your customers, which seems rare in this industry.
I agree with you on the speed point. I did not describe my complaint accurately. The router is currently working just as fast as before (or maybe minimally slower as you described. I cannot perceive a difference).
However, there is significant reduced capacity. And, the whole reason for building this sized router was anticipated growth. I expect 800 PPPoE sessions (up from 400) within 2 months time. Also, I’ve learned to never run a router/server at even close to 100% capacity if you want reliability.
The biggest issue is that I can find no where in the documentation that mutli-cpu is unstable. Please direct me to the documentation if I have just overlooked it. If this feature is unstable, why is it enabled by default? Why is the feature even included in a “stable” release of RouterOS? I can understand an unstable feature included in a beta release, but you would never find me running a beta release on my core router!
Also, my router crashed late last night even though multi-cpu is off. Traffic was still passing, but no PPPoE sessions could negotiate, all SNMP requests were ignored, local queue graphs went blank. I could not winbox nor SSH into the server. I had to power cycle it to regain access. So, something is still up. The router I replaced with this server (an AMD Athlon), ran perfect for more than 2 years on multiple versions of ROS. The latest being 3.13. I am running 3.16 on my new router.
Also, my router crashed late last night even though multi-cpu is off. Traffic was still passing, but no PPPoE sessions could negotiate, all SNMP requests were ignored, local queue graphs went blank. I could not winbox nor SSH into the server. I had to power cycle it to regain access.
\
sounds like the memory leak I’m trying to figure out on 2.9.51. once the router is over 380mb memory it will stop responding to management. once its a little higher it will crash.
The CPU, Memory and Disk Usage graphs did not stop recording during the event. And, it shows my max memory usage at only 56MB. I have 2G in the server. It could be the graph is inaccurate, but it does not appear my memory usage is to blame. My average usage is 47MB, so the high of 56MB does not seem to be abnormal.
I’d just like to point out that ~50MB of memory usage is quite nice considering the load on this router. Very efficient use of that resource!
Same issue here. Had always had problems with faulty speed reporting on interfaces in Winbox. Yet, by upgrading from 3.14 to 3.16 got much worse. Now, every time we reboot the PC-based MT, a different range of speed reporting occurs. At first upgrade, we got very high speed results such as 8Mbps on 1 Mbps lines. By rebooting, now we get only 30-60 kbps reporting. And so on with every reboot.
Actually, faulty reporting is affecting the queues for QoS purposes. This means real speeds are not only displayed improperly, but also perceived improperly by MT.
MT guys, you might have a bug here. How can queues work properly when the speed is not interpreted correctly?
Over the weekend, my new pc based router has taken it upon itself to reboot at random times. It happend once each day on Saturday and Sunday. I expect the same thing again this afternoon. I log to a remote syslog server, and there is nothing in the logs that would point to why this is happening. No abnormal CPU usage, nor memory usage, nor traffic. I’ll gather details and send in a support ticket later this morning and post here with results, if any.
from v3.6 to v3.11 we have had good luck with Multi-core, after that, hard power cycles are required. Sometimes it runs for days, some times weeks, but it will require a power cycle eventually. We have not been recommending more than 3.12 for a while.
Of course, I am with everyone else, come on guys. Just cause the Routerboard products do not have mutli-core does not mean your client base does not need multi-core CPU systems! When you start running 3 GigE BGP sessions, full routing tables, 8000 clients behind the router, with over 50,000 pps and avg of 200-300 meg of traffic, we need to have multi-core, as single core systems just can’t keep up!
?