[54250] in North American Network Operators' Group
Re: Cogent and Level3 Peering Issues
daemon@ATHENA.MIT.EDU (william@elan.net)
Wed Dec 18 15:41:37 2002
Date: Wed, 18 Dec 2002 12:16:27 -0800 (PST)
From: <william@elan.net>
To: <nanog@merit.edu>
In-Reply-To: <Pine.LNX.4.10.10212181521480.22955-100000@s1.yuriev.com>
Errors-To: owner-nanog-outgoing@merit.edu
Thing is if your connection is completely full one way, it'll effect
traffic the other way too. It should not be happening with syncronyous
connections, but practical observation is that it does! I suspect router
hardware is to blame (possibly packet cache is way full) and I'v seen
it happen only if you try to send 100% more traffic then link can handle
(just 100% traffic does not efect it - have to really push it), this
happened on 100Mb and even on Gb interface.
On Wed, 18 Dec 2002 alex@yuriev.com wrote:
>
> > > Me thinks Cogent doesn't have a problem with congestion on the inbound
> > > direction. Fix your reverse path.
> >
> > Customers of Cogent should be/are more concerned about congestion on the
> > inbounds at Level3 <-> Cogent; outbound is way too easy to control.
>
> Cogent has a pile of available inbound - websites tend to send traffic out,
> not take traffic in.
>
> Alex
>
