[125386] in North American Network Operators' Group
Re: Router for Metro Ethernet
daemon@ATHENA.MIT.EDU (Tony Varriale)
Wed Apr 14 00:12:56 2010
From: "Tony Varriale" <tvarriale@comcast.net>
To: <nanog@nanog.org>
Date: Tue, 13 Apr 2010 23:12:25 -0500
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Cisco rates it at 256mbps which places it above a NPE-400.
The 3825 says 179mbps on their spec sheet. Not sure where you are getting
your numbers but they are way off.
All of those numbers are straight forwarding with nothing turned on and 64
byte packets. That way you get a nice idea of what the CPU can do.
tv
----- Original Message -----
From: "Bill Stewart" <nonobvious@gmail.com>
To: <nanog@nanog.org>
Sent: Monday, April 12, 2010 1:27 PM
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 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.
>
