We have made a new RouterOS build that supposedly fixes some issues that caused multicore systems to crash. If anyone is interested to test their previously crashing Xeon, i7, Core2Duo or any other machine with several processing parts, please contact support for a test package.

what modules of RouterOS does this fix affect? I have v3.22 on Core2Duo, works pretty stable (some previous versions of v3 tested with multi-cpu=yes were crashing)

layer7 or address lists related

I don't use layer7, but have more than 600 address lists entries, and some are changing from day to day - still no problems with multicore. and it's our Internet router (with PPP and Queueing). internal core routers uses even higher number of address-lists entries, they did not expirience multicore issues even on early v3 =) am I lucky?

very nice. well some people had problems, so we fixed them

Does this also fix issue with the cpu's spikeing to 100% usage and locking up the dude?

which issue?

I had problems with QoS (address list and l7 related). I might be interested on it
But i experienced BGP issues too.

sure?? you fix it. this is a very good news. can you sent that version because i had 4 mikrotiks level 6 all in multicore = no because they always crash. please sent that version i am very very very interest on it

Normis what is that version?. Because i sent a email to support and they said that all version are on the web.

did you mention this topic? it's not version but package for 3.23, I believe...

My friend 111111 said that AMD never crashes bur Intel does :Р for multicore

It is a pre-release version of 3.24 (just few days older than one with PCC). Also there is winbox support for PCC included.

Regarding SMP - router that was crushing once or twice every day is up and running for 5 days now. (have 5 layer-7 filters and ~1000 address-list entries)

My friend 111111 said that AMD never crashes bur Intel does :Р for multicore

maybe that's wright
i have core 2 due Intel 2.8
my cpu 3% then 15% and totter between these numbers ...

when that happen its continue until restart my MK .. when i restart the MK work fine ... then i don't the cause...without reason

its return to totter again .
2ms between all this picture !
not normal at all

dormador, are you running the latest v3.24? if not, please wait until it's released. what I said applies only to v3.23

yes Mr.Normis

am running v3.23 I will be wait v3.24 i think it will be great .

HP server with Xeon QuadCore, crashed after 6hours - MT 3.24

With multu-cpu=no - works stable

Please send a supiut.rif to support.

Did you test the machine with stresstest, for example StressPrime 2004 Orthos, so you would be sure that the RAM is fine and the cooling is OK?

Hi.

I have crashes on every multicore router (more than 10 in network).
Only solution is set multi-cpu=no

- 2 HP servers,
- Supermicro motherboards with Xeons QuadCore and Core2Quad

so that is no problem with ram or temperature for sure

some times ago I sent supout file, they told me that I have to much simple queue rules...
I have disame problem on router with 10 simple queue rules

regards

most people that reported crashes before, now have them all fixed with v3.24. I suspect there is something different in your setups, maybe configuration, maybe some specific motherboard family ...

Hardware:
Supermicro X7SBL-LN1 Motherboard
2GB DDR2-800MHz ECC Kingston CL5 kit 2x1GB
Intel Quad-Core Xeon X3360 / 2.83 GHz processor
Intel PRO/1000 PT Dual Port Server Adapter (EXPI9402PTBLK)
SSD Patriot 32 GB

Routeros 3.23

I noticed that there is a problem with routers where we use hotspots
there is no problem with router that only passtrough packets (no hotspot, no firewall rules, no queues) - one case

bakula: that router from picture - do You have hotspot/queue rules there?

PS. sorry for me english...

bakula: that router from picture - do You have hotspot/queue rules there?

queue tree
firewall
adress-lists
mangle
nat
dhcp

no hotspot, no layer7

installed packages: advanced-tools,dhcp,ntp,security,system

the same needs as bakula have, the same uptimes =) will try Supermicro soon - hope not to face a problem

Hi,

I turn to multi-cpu=no, crashes on hotspot, Dell ML2900 with Xeon QuadCore,
so that is no problem with ram or temperature ROS 3.24.....

so... we have a clue bad bad hotspot

I've tried multi-cpu=yes on v3.24 and had similar issues, all of the systems i've been trying on have been running the hotspot.

I've also sent a couple of supout's over to mikrotik support, hopefully it'll help get the problem sorted

It's either Hotspot, VLAN or Simple Queues. Can you experiment with these features to narrow it down? Hotspot also uses Queuing and it can be run on VLAN

haha, oh wow. I have all 3 on mine :-/

I can confirm that with an NEC Express server, Pentium 4 with Hyper Threading that any version of Routers os greater than 3.11 will lock up hard when HOTSPOT is enabled.

If I disable that package then the machine runs fine, Vlans and Queues work ok.

Enable the hotspot package and the machine locks hard about 5 seconds after the boot up tones. Then the only way to recover the machine is to remove the interface that the hotspot listens on and restart the machine. Removing the interface causes the HOTSPOT to be disabled, and then the machine will run. At this point I must downgrade to 3.11 to get a working machine, and put the Hotspot interface back in again.

I tried the 3.24 but not the 3.25 yet.

Regards

Alex

We have tried for our second time in about 6 months using hotspot on version 3 with x86.

Version 3.24 on an Intel Core 2, and version 3.25 on a Athlon X2. Both boxes have the same configuration.

Both boxes last anywhere from 12 to 24 hours before locking up. we are now going back to 2.9.

Multi-cpu set on and off.
Hotspot
Simple Queues
Vlan's

I can't wait to see this fixed we really need a fast box for hotspot.

Tim

Are your x86 machines tested before installing RouterOS on them? Did you stress test CPU + Memory? Is cooling sufficient? What about power - is it stable? You have to check for all these first. Because a lot of problems were solved by replacing RAM for example. When they tested it and knew it was not working.

No I have not specifically run those tests on the machine. Its an interesting point though.

The specifica machine I have in mind was installed in production as a mikrotik core router in 2006 with RouterOS version 2.9.something, and we have been progressively upgrading it since then, whilst always keeping a few versions behind. Its always been stable, but I guess things can change.

Its difficult to take this machine out of production to run those tests, but let me find a spare router and try it out.

Could just use Made for Mikrotik Products too. We have had stable SMP support since 3.11..

Ah! Its Denis Burgess flogging his wares again.

Denis, before you go around making those comments take a little time to understand where the people are coming from.

Here in Africa (kenya in my case) it is not possible to buy your products. Yes I could import one and have it DHL over here but import duties are so high on something like that that it would be cheaper for me to buy Cisco.

Yes, thats right cheaper to buy cisco! They are a bigger company with a presence in Kenya and are able to use their slush funds effectively to ensure cheaper duties.

So, in the meantime guys like us manage with other solutions.

Something to think about: In kenya a 1mb up and down pure dedicated internet link via Vsat costs 3500 US Dollars per month.

Do me a favour and keep your marketing off the mikrotik forum.

Regards

Alex

P.s. apologies to all other people who read this thread. Feel free to flame me at info @ itworx.co.ke or block me from the forum. I am tired of Denis Burgess and his forum sales.

alex_rhys-hurn tnx for the reality check

Denis thank you for the useful info. I could totally buy your stuff regardless of shipping costs. Its a principle thing. Its god to know what is stable and what not so tnx for the info.

Keep in mind that we do have a distributor in Africa, so you don't have to ship it form the US. Second, if you are using a 1 meg connection, why have a x86 at all! a 493AH would handle 99% of what you need and its super cheap and stable, vs messing with unsupported systems.

You buy Cisco cause you put it in and it works. You buy router boards and powerrouters for the same! If you buy a server and place RouterOS on it without fully testing it, you are in a crap shoot. It may work for a while, but is it cheaper ? Not really due ot the support time involved and maintaining it.

With that said, something to help the fourms, our 2282, Dual Quad Core Xeon Systems is working perfectly with 3.25 .. before that we had to go back to 3.6 I believe. But a bit more testing.

As Juniper Elite partner we often come across companies where network purchasing decisions are made on the "no teal no deal" basis. For some reason a lot of people believe that Cisco is the only networking product that actually works!

Although I also do not agree with Dennis blatantly promoting his PowerRouter product via the user forums, I commend him for building and supporting a product that works. Maybe there is a better way for him to promote his product to Mikrotik users that will not offend people on the forum?

Ya know, you can't make everyone happy. Some people are more than happy to find something that is supported and tested, and others are just offended for someone recommending something other than what they have. But if you will notice, I also saw that they only had a meg of bandwidth, and I recommended that they use a 400AH series! Routerboard will more than handle that amount of load! I recommend what is necessary!

You are saying it has nothing to do with hardware/memory, and yes, i would agree that it "should" work. However, the fact is that it don't with YOUR hardware. So guess what, if you go buy other platforms, i;.e cisco, juniper, you can't put their software on your "DELL". So now you have to buy their hardware/software as a substantial price increase.

The whole point with RouterOS is that you can put it on your hardware, but if you want to put it on hardware that is not tested, etc, then you are making the decision to do so.. I suggested to use hardware that we know works with mulit-core and you won't have that issue.

There is more than "it's also Linux, so it should work!". If you must complain, do it to support, not here. Topic will be locked because some people can't control their aggression.