Mr Mikrotik, when you see so many posts, means you really have something to do.
Of course I'll provide supout when asked. Even read-only access.
winbox , work worse on routing-test package
if I try change some rules, cpu go to 50%, and need much more time, 30-40 sec
with standar package go to 50%, but end job in 5-10 sec.
3 peer, 3 full table. about 900k prefix/routes
Is it actually crashed (autosupout was generated)? Or ospf was unable to receive hello packets? Try to increase OSPF dead-interval, it might help.Hello!
3.24 is out.. i've tested it.. in lab ( with a REAL full table ) i've setup an ibgp link between two RB1000.. i've do 8 test ( enable and disable peer, or reboot.. )
in 5 case rb1000 works ok, 280k prefix getted in 40 seconds ( cpu 100% ) ospf is ok, winbox also
in 3 case winbox close and cpu go to 100% for 4 o 5 minutes,, and of course.. ospf CRASH.
i think the problem is partially fixed..
the bug persists
PS: ROUTING-TEST of course
PS2: Please mikrotik FIX FIX FIX the bug!!!
3.30 routing-test is workingHi,
I need to get 100,000 BGP prefixes with a RB1000U.
Right now I run on ver. 4.4 RouterOS.
My router crashed, when we tested now, I waited 5 minutes, and no response from router, maybe freezed when receive the prefixes.
I read that RB1000 works on 300k prefix too. Maybe some delays on getting prefixes.
If somebody use RB1000 with BGP >100k prefixes, please tell me witch version of RouterOS is the best?
It's very important form me, my clients are down.
I'm no expert, but I think you're a little off in your diagnosis. RouterOS has to perform its route selection algorithm first before any routes are installed in the kernel's FIB. Routing daemons normally run in user-space, process routes in the various RIBs, then install the best paths in the kernel's FIB.mikrotik needs to decouple the BGP process from the linux kernel. this means it takes more RAM, but okay.
I had a small linux-box (600MHz VIA) with quagga which does not show this behavior at all.i think, mikrotik must use bird bgp daemon, as its one of the best bgp daemons and kicks quagga ass! it was if i recall correctly the only bgp daemon that supported tests that crashed quagga.
it seems to me that it is not the route filters themselves, but merely a winbox issue.It looks like BGP can become slow if routing filters are changed. Anyone who experience BGP problems after routing filter changes, please contact support and specify what routing filters you had and what changes you have made.
Thanks for the info!I posted earlier in this thread - I am running Ros4.8 on a RB1000 with 3 full BGP feeds. We're down the 414M of RAM, that seems to be close to when the router crashes. I am generating a support.rif file (which has been over 5 minutes now and still waiting) and I'm going to submit to Mikrotik. I like Mikrotik, but the entire 4.xx releases have been flawed in my opinion for BGP. I hope they can fix this issue as it's limiting what I can do with a mikrotik router
If I knew that specific things would cause stability issues then I would avoid it and see if it still meets my needs. Open discussion and knowledge sharing from the company would take the guessing game out of it.why then this 'russian-style' denial and deception about bugs? Do the bugs go away if you hide them?
action time out - try again, if error continues please contact MikroTIk support and send supout file (13)
action timed out - try again, if error continues contact MikroTik support and send a supout file (13