nanog mailing list archives
RE: router startup behavior
From: Paul Donner <pdonner () cisco com>
Date: Mon, 14 Jan 2002 15:49:50 -0500
how long would you wait for? At 03:32 PM 1/14/2002, David Schwartz wrote:
On Mon, 14 Jan 2002 13:28:42 -0600, Steve Naslund wrote: >Here is my best guess as to what you are seeing. Most likely a large CIDR >block is announced by a service provider A. A small CIDR block is given to >a customer who is connected to multiple service providers and thus running >BGP. Now the more specific route is announced by service provider B, he >does not own the block but is announcing it on behalf of service provider As >customer. What is happening is that the customer has a line or router >failure and that withdraws their more specific announcement from service >provider B. Since the service provider A is announcing a supernet route he >now becomes the only route for that block.If that's the problem, a fix might be to not advertise any routes to a BGPpeer until you receive all the routes that peer has to send you. I think it's elegant that when two routers connect, neither sends any routes to the other until each has received all the routes the other has to send. Very Zen, don't you think? DS
Current thread:
- router startup behavior Ratul Mahajan (Jan 14)
- Re: router startup behavior Jared Mauch (Jan 14)
- RE: router startup behavior Steve Naslund (Jan 14)
- RE: router startup behavior David Schwartz (Jan 14)
- RE: router startup behavior Randy Bush (Jan 14)
- Re: router startup behavior Valdis . Kletnieks (Jan 14)
- Re: router startup behavior Paul Donner (Jan 14)
- Re: router startup behavior Valdis . Kletnieks (Jan 14)
- RE: router startup behavior David Schwartz (Jan 14)
- Re: router startup behavior Yakov Rekhter (Jan 14)
- RE: router startup behavior Paul Donner (Jan 14)
- Re: router startup behavior Pierfrancesco Caci (Jan 14)
- Re: router startup behavior Lincoln Dale (Jan 15)
- <Possible follow-ups>
- RE: router startup behavior Steve Naslund (Jan 14)
- RE: router startup behavior Borchers, Mark (Jan 15)
- Re: router startup behavior Havard Eidnes (Jan 16)
- FW: router startup behavior Borchers, Mark (Jan 15)
- Re: FW: router startup behavior Simon Lockhart (Jan 15)
- Re: FW: router startup behavior Jared Mauch (Jan 17)
- Re: FW: router startup behavior Stephen Griffin (Jan 18)
- Re: FW: router startup behavior Simon Lockhart (Jan 15)