[189007] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Friday's Random Comment - About: Arista and FIB/RIB's

daemon@ATHENA.MIT.EDU (Ryan Woolley)
Fri Apr 29 12:00:06 2016

X-Original-To: nanog@nanog.org
In-Reply-To: <572361E4.2060608@foobar.org>
Date: Fri, 29 Apr 2016 12:00:02 -0400
From: Ryan Woolley <rwoolleynanog@gmail.com>
To: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

Just to be clear, this isn't (to my knowledge) something that Arista is
doing and so the risk described doesn't affect the products that were
discussed on that thread.

On Fri, Apr 29, 2016 at 9:30 AM, Nick Hilliard <nick@foobar.org> wrote:

> Laszlo Hanyecz wrote:
> > I'm curious about specific failure modes that can result from this, if
> > anyone can share examples/experience with it.
>
> The canonical pathological case is where the deaggregated prefixes are
> affected by upstream topology changes and suddenly your optimisations
> which saved you N% of forwarding lookup table capacity are wiped out to
> zero and you end up with no ability to look up next-hops.
>
> Nick
>

home help back first fref pref prev next nref lref last post