[28908] in North American Network Operators' Group

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

Re: That pesky AS path corruption bug...

daemon@ATHENA.MIT.EDU (Vadim Antonov)
Tue May 23 15:55:27 2000

Date: Tue, 23 May 2000 12:53:20 -0700
From: Vadim Antonov <avg@kotovnik.com>
Message-Id: <200005231953.MAA02205@kitty.kotovnik.com>
To: wrath@cs.umbc.edu
Cc: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu


Vijay Gill <wrath@cs.umbc.edu> wrote:

> This is what BGP dampening is for.  Dropping a few prefixes here and there
> is a good way to make operational debugging of a network of any size,
> hell.

Dampening reduces negative effects, but there's still a potential for
serious service disruption: processing a ton of new updates ties up
CPU resources which in case of OFRV software can easily cause timer expiration
on BGP sessions of peers border routers.

> With a NOTIFY and a drop, there is a definite positive feedback that
> something is majorly wrong and allows people to open top level cases with
> vendors.

I do not think that deliberately breaking things just to attract attention
of the management is a good idea.  If some vendor ignores bug reports, go
to a different vendor :)

--vadim


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