[76506] in North American Network Operators' Group
Re: Affects of rate-limiting at the far end of links
daemon@ATHENA.MIT.EDU (Alex Bligh)
Mon Dec 13 09:00:23 2004
Date: Mon, 13 Dec 2004 13:57:26 +0000
From: Alex Bligh <alex@alex.org.uk>
Reply-To: Alex Bligh <alex@alex.org.uk>
To: Sam Stickland <sam_ml@spacething.org>, nanog@nanog.org
Cc: Alex Bligh <alex@alex.org.uk>
In-Reply-To: <Pine.WNT.4.61.0412131304390.2640@tech1.office.toastedmedia.net>
Errors-To: owner-nanog-outgoing@merit.edu
--On 13 December 2004 13:18 +0000 Sam Stickland <sam_ml@spacething.org>
wrote:
> doesn't lock out traffic for such long periods of time.
>
> Could it be that buffers and flow-control over the 14ms third party leg
> are causing the rate-limiting leaky bucket to continue to overflow long
> after it's full?
Or you are losing line protocol keepalives of some sort (e.g. at L2), or
routing protocol packets. It may also be that your MPLS provider limits
the traffic at X kbps INCLUDING protocol overhead - if so it's going to
police out all sorts of important stuff (assuming you are running FR, ATM
or something rather than some sort of TDM over MPLS).
Alex