[195680] in North American Network Operators' Group
Re: Max Prefix Out, was Re: Verizon 701 Route leak?
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Fri Sep 1 14:57:36 2017
X-Original-To: nanog@nanog.org
In-Reply-To: <73650B14-9A69-4023-880A-98391CE5418C@ianai.net>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Fri, 1 Sep 2017 11:21:14 -0400
To: "Patrick W. Gilmore" <patrick@ianai.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Fri, Sep 1, 2017 at 7:56 AM, Patrick W. Gilmore <patrick@ianai.net>
wrote:
> On Sep 1, 2017, at 5:26 AM, Randy Bush <randy@psg.com> wrote:
> >
> > i have 142 largish bgp customers, a large enough number that the number
> > of prefixes i receive from them varies annoyingly. how do i reasonably
> > automate setting of my outbound prefix limit?
>
> First, it seems you know the inbound so automating the outbound is simple
> arithmetic.
>
>
I would have said the same... i ought to know high-water marks for your
inbound peer count(s), and can work out a +20% outbound...
you also probably can survey your outbound peerings and +20% some
high-water mark there, or make a 'meet in the middle' between the
inbound-math and outbound-math.
> But even if that is unruly, setting the outbound to, say, 300K or so would
> keep you from spilling a full table. Not perfect, but better than nothing.
>
> Orrrrrr, perhaps this feature is not for you?
>
> --
> TTFN,
> patrick
>
>
