plz dont go with 3825/3845 unless you need it for voice etc. we have clients run 3825/3845 and they don't work properly beyond 50mbps with traffic shaping.
On Wed, Apr 14, 2010 at 12:12 AM, Tony Varriale <tvarri...@comcast.net> wrote: > 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" <nonobvi...@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.eb...@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. >> > > >
