[c-nsp] Problems with peers that don't have full routing tables

[Bob Tinkelman]

> On Fri, Mar 02, 2007 at 03:00:45PM -0400, Bob Tinkelman wrote:
> >   I don't want to tell the customer to not announce the /20
> >   but instead announce lots of /24s, though that would solve
> >   this particular issue.

> Have the customer announce the /20 and the /24 to you, and offer
> them a "do not export the /24 further" BGP community.

Thanks Gert. 

We have communities defined to support this and I should
have included it as an option in my list.  I expect this is
what our customer will choose.

One of the reason's I posted was that my first reaction
after fixing the immediate problem was to look for a way to
be proactive in avoiding similar problems in the future, or
at least noticing them before our customers complained.

Now that I know that one of my peers is configured "with
partial routes and a default pointing elsewhere", I should
be able to write a script looking for problem cases:

   A net we're announcing to a peer, with a
   subnet which we route to an upstream.

At this point, my plan is to write such a script, get
daily(?) reports of this condition, and address them one
by one, probably by advising our customers to use our
communities as you suggested.

Again, thanks for pointing out this option.
--
Bob Tinkelman          <bob at tink.com>
ISPnet, Inc.  http://www.ispnetinc.net

+1 (718) 464-4747  office
+1 (800) 806-NETS  toll free
+1 (718) 217-9407  fax