We run a 3845 at over 300 Mbps and it's less than 50% CPU....most times less than 30%. No BGP, just OSPF.
Frank
-----Original Message----- From: Bill Stewart [mailto:nonobvious@gmail.com] Sent: Monday, April 12, 2010 1:27 PM To: nanog@nanog.org Subject: Re: Router for Metro Ethernet
On Mon, Apr 12, 2010 at 10:55 AM, Dylan Ebner <dylan.ebner@crlmed.com> wrote:
However, this router also has 2 100mb connections from local lans
They just added IPv6 over PPP Support in v5 too :) ----------------------------------------------------------- Dennis Burgess, CCNA, Mikrotik Certified Trainer, MTCNA, MTCRE, MTCWE, MTCTCE, MTCUME Link Technologies, Inc -- Mikrotik & WISP Support Services Office: 314-735-0270 Website: http://www.linktechs.net LIVE On-Line Mikrotik Training - Author of "Learn RouterOS" -----Original Message----- From: Owen DeLong [mailto:owen@delong.com] Sent: Monday, April 12, 2010 11:13 PM To: frnkblk@iname.com Cc: nanog@nanog.org; 'Bill Stewart' Subject: Re: Router for Metro Ethernet I stand corrected on the Mikrotik... Apparently, while not well documented, they do, indeed support IPv6 and their Wiki even includes tunnel configuration information. Apologies to Mikrotik (and some encouragement to add this to your main-line documentation). Owen On Apr 12, 2010, at 8:56 PM, Frank Bulk wrote: that it
is also terminiating.
For our 100mb metro e connections we use 3845s. The 100 mb service terminates into NM-GEs, which have a faster throughput than the hwics.
Be careful using 3845s for 100 Mbps connections or above - Cisco rates them at 45 Mbps (and 3825 at half of that) but last time I checked doesn't make any promises at faster than T3. They're being conservative about it, but one thing that really can burn the horsepower is traffic shaping, which you need with some MetroE carriers.
-- ---- Thanks; Bill
Note that this isn't my regular email account - It's still experimental so far. And Google probably logs and indexes everything you send it.