Brad,

I second your claim of high capacity Linux routers. (my comments are not 
specific to MT)
Our newest generation of Linux Routers are easilly passing 4-5Gbps through 
it.

The secret to fast Linux routers was several fold. The first was to get to a 
2.6 kernel, and NAPI support on drivers.
The other was to get quad core processors, if multiple Bus slots were used. 
The reason being bus slot tends to assign itself under the control of 
adifferent Processor core.
With straight traffic passing, they really fly.

The weak link though is teh limited Intel clock.Many badnwdith management 
techniques time around the clock limited to 100 ticks per second. This can 
majorly limit bandwdith management routines that run on the routers. (For 
example typical HTB setting ideal for 1-5 mbps speeds, start having problem 
once 10mbps is reached. Customization is needed to handle the higher speeds. 
It can handle the badnwdith management of the higher speeds (100mbps to end 
user) well also, but then as a side effect it has problems with lower speed 
circuits.  In otherwords it gets hard to have the same router than manages 
100mbps circuits to also manage 1-2mbps well.  Anyway, I'm sure many of 
these things can be solved by smarter bandwidth mangement configurations. 
However, for some routers applciations, to get full capacity of the router 
(our cores), we opted to bypass any bandwdith management, and use it like a 
switch, and only do Bandwdith Management on the cell routers closest to the 
csutomer.

But it can really be sweat using Linux fo BGP routers, expecially if you 
plan to process alow of BGP session/tables for BGP to the custoemr.

I do not have secific experienmce with exactly what MT can do, but I'm sure 
its near equivellent on similar hardware platforms.

Tom DeReggi
RapidDSL & Wireless, Inc
IntAirNet- Fixed Wireless Broadband


----- Original Message ----- 
From: "Brad Belton" <[EMAIL PROTECTED]>
To: "'WISPA General List'" <wireless@wispa.org>
Sent: Tuesday, December 09, 2008 11:40 PM
Subject: [WISPA] MikroTik Multi-GigE and greater throughput... (was 
CiscoVLAN help)


>I didn't want to hijack Travis's Cisco thread, but wanted to throw in my 
>.02
> regarding MikroTik as a core router.
>
>
> We began running MikroTik as a core router sometime back in 2004 when our
> Cisco VXR DS3 router started to struggle.  We purchased a couple LMC DS3
> NICs from Eje at Wisp-Router and haven't looked back since.
>
> It was better than three years ago when we bench tested more than 800Mbps
> between MikroTik routers using older Intel Pro fiber NICs and standard 
> 32bit
> PCI slots.  Over the years we have deployed numerous MikroTik routers with
> 24 or more 10/100 Interfaces, and several MikroTik routers with multiple
> Intel GigE Copper and Fiber Interfaces.
>
> Today our MikroTik routers have evolved to include motherboards with
> multiple PCIe x8 & x16 lane expansion slots, Quad core CPUs, 2Gig RAM,
> redundant hot-swap power supplies and multiple six port SFP NICs.  This
> latest generation of MikroTik router we are deploying are extremely fast,
> flexible, cost effective and most importantly reliable.
>
> The SFP NICs allow us to easily swap Interfaces from Copper GigE to SX
> fiber, LX fiber, ZX Fiber...all hot-swap without requiring the router to 
> be
> powered down or rebooted.  The power supplies are diverse and redundant. 
> We
> can lose either power feed or power module or any combination of the two 
> and
> still keep the router powered up.
>
> We are currently peering with three GigE upstream providers with a fourth
> GigE provider being turned up this week for unprecedented capacity and
> diversity for an ISP our size.  We are already exploring and evaluating
> 10GigE Interfaces as our requirements continue to increase.  We have no
> reason to believe the MikroTik platform will not continue to deliver the
> exceptional performance we have become accustomed to.
>
> Every client gets a MikroTik CPE router that we own and manage regardless 
> of
> the medium used (microwave, copper, fiber etc.) to deliver their data
> circuit.  A MikroTik as a client CPE router gives us terrific flexibility
> and diagnostic abilities.  MikroTik allows us to provide the detailed
> information required to identify and resolve problems at the client side
> quickly and efficiently.  We have made countless "IT Guys" heroes in the
> eyes of their employers more times than I care to remember.  <grin>
>
> I firmly believe we would not be where we are today, offering the level of
> service we are able to provide without MikroTik at the core of our 
> network.
>
> Best,
>
>
> Brad
>
>
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Gino Villarini
> Sent: Tuesday, December 09, 2008 8:42 PM
> To: WISPA General List
> Subject: Re: [WISPA] Cisco VLAN help
>
> We are using HP Carrier Servers on our Core, Dual Xenon 2.8 Ghz, Dual
> PS, 2 GB Intel Nics with 3 PCIX 3 Port GB Cards for a total of 14 ports
> per Router
>
>
> Gino A. Villarini
> [EMAIL PROTECTED]
> Aeronet Wireless Broadband Corp.
> tel  787.273.4143   fax   787.273.4145
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Mike Hammett
> Sent: Tuesday, December 09, 2008 10:38 PM
> To: WISPA General List
> Subject: Re: [WISPA] Cisco VLAN help
>
> I answer with a question.  What makes you think they couldn't do 100
> megs?
> I believe the original PowerRouter series does 5.9 gigabits and the
> latest series does 8 gigabits.
>
> I don't know how strong Mikrotik's VPLS offering is, but from what I've
> heard, VPLS is the way to go.
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> --------------------------------------------------
> From: "Josh Luthman" <[EMAIL PROTECTED]>
> Sent: Tuesday, December 09, 2008 8:13 P
> To: "WISPA General List" <wireless@wispa.org>
> Subject: Re: [WISPA] Cisco VLAN help
>
>> How can you possibly get 100 megs with Mikrotik?
>>
>> On 12/9/08, Dennis Burgess - LinkTechs <[EMAIL PROTECTED]>
> wrote:
>>> I like the "THEY ARE PAYING FOR IT"!  :)  Nothing wrong with that.
> You
>>> should be able to do that with some high end MTs and EoIP Tunnels
> though
>>> :)
>>>
>>> ------------------------------
>>> * Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer
>>> Link Technologies, Inc -- Mikrotik & WISP Support Services*
>>> 314-735-0270
>>> http://www.linktechs.net <http://www.linktechs.net/>
>>>
>>> */ Link Technologies, Inc is offering LIVE Mikrotik On-Line Training
>>> <http://www.linktechs.net/onlinetraining.asp>/*
>>>
>>>
>>>
>>> Travis Johnson wrote:
>>>> Hi,
>>>>
>>>> Normally that is what we do... using Cisco ASA firewalls and setting
>>>> up VPN tunnels for the customers... however, this particular
> customer
>>>> needs the full 100Mbps between the ports and "transparent"
>>>> transport... and they are paying for it... :)
>>>>
>>>> Travis
>>>> Microserv
>>>>
>>>> Dennis Burgess - LinkTechs wrote:
>>>>> Just a FYI, I would just create a tunnel between the two sites.  No
>>>>> configuration on your backend network, bandwidth restrictions are
> the
>>>>> same as internet traffic typically, etc.  Simpler, and no "loop"
>>>>> issues.
>>>>>
>>>>> ------------------------------
>>>>> * Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer
>>>>> Link Technologies, Inc -- Mikrotik & WISP Support Services*
>>>>> 314-735-0270
>>>>> http://www.linktechs.net <http://www.linktechs.net/>
>>>>>
>>>>> */ Link Technologies, Inc is offering LIVE Mikrotik On-Line
> Training
>>>>> <http://www.linktechs.net/onlinetraining.asp>/*
>>>>>
>>>>>
>>>>>
>>>>> Travis Johnson wrote:
>>>>>
>>>>>> Ok... found the original problem... a few switches did not have
> the
>>>>>> vlan
>>>>>>
>>>>>> setup in the vlan database. So the VLAN is up and working now...
> but
>>>>>> the
>>>>>>
>>>>>> problem is because we have a "ring", we use Spanning Tree to keep
> from
>>>>>> having a loop in the network. But when we bring up the VLAN, the
>>>>>> spanning-tree does not start blocking the VLAN traffic. It does
> block
>>>>>> the "normal" VLAN1 traffic (like it always has), but the new VLAN
>>>>>> never
>>>>>> gets "blocked", so it creates a loop around the ring.
>>>>>>
>>>>>> Am I missing something? I've checked the settings and can't find
>>>>>> anything that I missed to make it work...
>>>>>>
>>>>>> Travis
>>>>>> Microserv
>>>>>>
>>>>>> Eric Rogers wrote:
>>>>>>
>>>>>>
>>>>>>> Try a "show interface fastethernet x/y switchport" and see what
> is
>>>>>>> the
>>>>>>> status of the port and that trunking VLANs enabled are also
> trunking
>>>>>>> VLANs active.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
>>>>>>> On
>>>>>>> Behalf Of Travis Johnson
>>>>>>> Sent: Tuesday, December 09, 2008 5:17 PM
>>>>>>> To: WISPA General List
>>>>>>> Subject: Re: [WISPA] Cisco VLAN help
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> By default, when doing the switchport mode trunk, all VLAN's are
>>>>>>> allowed
>>>>>>> (I even issued the command "switchport trunk allowed vlan all"
> and it
>>>>>>> did not display on the sho conf afterward).
>>>>>>>
>>>>>>> Travis
>>>>>>> Microserv
>>>>>>>
>>>>>>> Patrick Shoemaker wrote:
>>>>>>>
>>>>>>> Travis Johnson wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I need some Cisco switch VLAN help.
>>>>>>>
>>>>>>> I currently have about 60 Cisco 3500 series switches connected
>>>>>>> via the
>>>>>>> GBIC ports all in a ring configuration with spanning tree. I am
>>>>>>> trying
>>>>>>> to setup a VLAN for a customer between two of the FastEthernet
>>>>>>> ports so
>>>>>>> they can connect their offices. I have port 5 on each switch
>>>>>>> setup in
>>>>>>> VLAN105 and every GBIC port on all the switches setup as
>>>>>>> trunking ports.
>>>>>>> There are 17 other cisco switches between these two.
>>>>>>>
>>>>>>> I have this setup between two other offices, but they are
>>>>>>> directly
>>>>>>> connected to each other, with no other switches in between.
>>>>>>>
>>>>>>> What am I missing?
>>>>>>>
>>>>>>> Travis
>>>>>>> Microserv
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
> ------------------------------------------------------------------------
>>>>>>> --------
>>>>>>> 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/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Is each trunk port in the path set to forward the VLAN with
> command:
>>>>>>>
>>>>>>> switchport trunk allowed vlan xxx
>>>>>>>
>>>>>>> A sh int for an example trunk and access port would be handy.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
> ------------------------------------------------------------------------
> --------
>>>>>>> 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/
>>>
>>
>>
>> -- 
>> Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>>
>> Those who don't understand UNIX are condemned to reinvent it, poorly.
>> --- Henry Spencer
>>
>>
>>
> ------------------------------------------------------------------------
> --------
>> 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/


--------------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG.
Version: 7.5.552 / Virus Database: 270.9.15/1839 - Release Date: 12/9/2008 
9:59 AM



--------------------------------------------------------------------------------
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/

Reply via email to