![nanog logo](/images/nanog-logo.png)
nanog mailing list archives
Re: That pesky AS path corruption bug...
From: Vijay Gill <wrath () cs umbc edu>
Date: Tue, 23 May 2000 16:03:39 -0400 (EDT)
On Tue, 23 May 2000, Vadim Antonov wrote:
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.
Set rwnd to 0 if you are temporarily resource constrained. If you are constrained on a normal basis, upgrade.
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 :)
Ah yes.... Layer 8 is always a problem. /vijay
Current thread:
- Re: That pesky AS path corruption bug..., (continued)
- Message not available
- Re: That pesky AS path corruption bug... Kai Schlichting (May 23)
- Re: That pesky AS path corruption bug... Daniel Senie (May 23)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Message not available
- Re: That pesky AS path corruption bug... Vadim Antonov (May 23)
- Re: That pesky AS path corruption bug... Peter T. Whiting (May 23)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Re: That pesky AS path corruption bug... Blaine Christian (May 23)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Re: That pesky AS path corruption bug... Jeff Haas (May 23)
- Re: That pesky AS path corruption bug... Vijay Gill (May 23)
- Re: That pesky AS path corruption bug... John Fraizer (May 23)
- Re: That pesky AS path corruption bug... Adrian Chadd (May 24)
- Re: That pesky AS path corruption bug... Michael Shields (May 24)
- Re: That pesky AS path corruption bug... Adrian Chadd (May 24)