[54251] in North American Network Operators' Group
Re: Cogent and Level3 Peering Issues
daemon@ATHENA.MIT.EDU (Petri Helenius)
Wed Dec 18 16:39:17 2002
Date: Wed, 18 Dec 2002 23:38:02 +0200
From: Petri Helenius <pete@he.iki.fi>
To: william@elan.net
Cc: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu
william@elan.net wrote:
>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.
>
>
Or could it be that your ACK packets just simply get delayed enough for
the traffic
to the other direction to suffer somewhat?
This is quite common phenomenan in asymmetric links but also exists for
symmetric
ones.
Pete
>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
>>
>>
>>
>
>
>
>
