This is exactly what I am concerned with..... Things breaking once in a while is not an issue.. Things breaking once every month or few weeks is not going to be acceptable from our users..
Trying to determine if this is a 'feature' or a short term 'bug'. Cisco's and Junipers, get a premium even in the used market place, but the primary reason for it is stability... Any other that can chime in with their experiences ? Many thanks in advance. Faisal Imtiaz Snappy Internet & Telecom On 11/2/2010 10:32 AM, Chuck Hogg wrote: > Our MikroTik BGP router keeps crashing about once every month or > so...sometimes sooner, sometimes later. We are using full BGP tables > and 4.11 currently. > > Regards, > > Chuck > > > > On Tue, Nov 2, 2010 at 10:23 AM, Brad Belton<b...@belwave.com> wrote: >> We've been running BGP with MikroTik for quite some time now. It hasn't >> been flawless by any stretch, but ever since late v2.8 or early v2.9 we >> haven't had much trouble with it. We running v3.30 on two routers with two >> full feeds each and a third running v4.11 with two full feeds. All of these >> routers have a handful of downstream BGP peers that we are also delivering >> full tables to. >> >> So far I think v4.11 might be the best, but we don't have as much time on >> that version as we do with v3.30. The only reason we moved one of our >> routers from v3.30 to v4.11 was because we had an unusual hang with that >> particular router. We weren't sure if it was hardware or OS related, >> however moving it to v4.11 seems to have resolved the problem. (knock on >> wood) >> >> Bottom line is given the price of a beefy MikroTik router vs. buying an >> Imagestream or Cisco that is equivalent we can have hot standby spares on >> hand and still be thousands if not tens of thousands of dollars ahead. That >> coupled with building a network that isn't solely dependent on any single >> point of failure further reduces the crisis when a core router fails. >> >> Things break...doesn't matter if MikroTik, ImageStream, Cisco or Juniper >> makes it. ALL things break eventually, so plan for it! >> >> Best, >> >> >> Brad >> >> >> >> >> -----Original Message----- >> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On >> Behalf Of Faisal Imtiaz >> Sent: Tuesday, November 02, 2010 9:11 AM >> To: n...@brevardwireless.com; WISPA General List >> Subject: Re: [WISPA] Full BGP on RouterOS >> >> Hi Nick, >> >> How stable has the Mikrotik been running full BGP with the two providers ? >> >> (I read about a memory leak issues, is that why you are using 5.0rc1 ?) We >> have been considering getting a Mikrotik for such use. >> >> Thanks. >> >> Faisal Imtiaz >> Snappy Internet& Telecom >> >> On 11/2/2010 9:21 AM, Nick Olsen wrote: >>> We have two full tables running on mikrotik, in two different locations. >>> >>> Running that command >>> /ip route print count-only where bgp-as-path="1234" >>> Replacing the AS with "33363" (local cable company). >>> Doesn't work on either of our routers for some reason (MT 5.0rc1 or 4.4). >>> >>> Our router running a core 2 2.93ghz can take two full feeds gets all >>> the routes in about 4 seconds, And cpu load is idle about 13 seconds >> later. >>> However making changes with routing filters take anywhere from >>> 10seconds to 2 minutes depending on what its doing. >>> >>> >>> Nick Olsen >>> Network Operations >>> (855) FLSPEED x106 >>> >>> >>> >>> ---------------------------------------------------------------------- >>> -- >>> *From*: "Kristian Hoffmann"<kh...@fire2wire.com> >>> *Sent*: Friday, October 29, 2010 11:50 AM >>> *To*: "WISPA General List"<wireless@wispa.org> >>> *Subject*: [WISPA] Full BGP on RouterOS >>> >>> Hi, >>> >>> Does anyone have 1-2 full BGP routing tables on a MikroTik router? If >>> so, what kind of hardware are you running. I'm testing a single feed >>> on a P3 800. It loads the routes fine, and seems to handle the routes >>> in stride (all 328659 of them), until you start poking at the routing >>> table like... >>> >>> /ip route print count-only where bgp-as-path="1234" >>> >>> An AS that yielded 500 routes took 1-2 minutes at 100% CPU to complete. >>> Is this "normal" these days, or is significantly greater hardware in >>> order? I used to have a full feed on a Cisco 3640. It took 5-10 >>> minutes to load all of the routes after a reload, and it was almost >>> impossible to log in, high packet loss, etc. during that time. >>> >>> So, should it take 10 seconds on real hardware, or is this type of >>> query always slow? >>> >>> Thanks, >>> >>> -- >>> Kristian Hoffmann >>> System Administrator >>> kh...@fire2wire.com >>> http://www.fire2wire.com >>> >>> Office - 209-543-1800 | Fax - 209-545-1469 | Toll Free - 800-905-FIRE >>> >>> >>> >>> >>> >>> ---------------------------------------------------------------------- >>> ---------- >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> ---------------------------------------------------------------------- >>> ---------- >>> >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >>> >>> >>> >>> >>> >>> ---------------------------------------------------------------------- >>> ---------- >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> ---------------------------------------------------------------------- >>> ---------- >>> >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> ---------------------------------------------------------------------------- >> ---- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> ---------------------------------------------------------------------------- >> ---- >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
