Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: router startup behavior

  • From: Paul Donner
  • Date: Mon Jan 14 17:50:54 2002

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 BGP
peer 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




Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.