[c-nsp] suppress bgp updates?

Wed Nov 17 17:35:20 EST 2010

Do you have the /24 actually announced or is this just for the test?  I ask because I use the tie-down routes for my /20's but then only have more specific routes in my internal table, so that the tie-down is only invoked when there is a catastrophic failure.  The tiedown won't work, as you have found, if your tiedown matches a route being injected into your table.

In your route-map example, I think you only use the origin-igp if you're using the aggregate-summary statement in our BGP configuration instead of the network statement configuration.  Perhaps that's what you're looking for.

Instead of 'network 192.0.2.0'  use 'aggregate-address 192.0.2.0 255.255.255.0 summary-only' and then set the origin igp in your route-map for the outbound announcement.

Mike
--
Michael K. Smith - CISSP, GSEC, GISP
Chief Technical Officer - Adhost Internet LLC mksmith at adhost.com
w: +1 (206) 404-9500 f: +1 (206) 404-9050
PGP: B49A DDF5 8611 27F3  08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Dale Shaw
> Sent: Wednesday, November 17, 2010 1:43 PM
> To: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] suppress bgp updates?
> 
> On Thu, Nov 18, 2010 at 7:40 AM, Dale Shaw
> <dale.shaw+cisco-nsp at gmail.com> wrote:
> >
> > What happens if you drop the administrative distance of your static on
> > 'edge' from 240 to something lower than 110?
> 
> .. A whopping great big black hole is what happens, as Mark politely
> pointed out to me off-list.
> 
> :-)
> 
> Duhh.
> 
> Cheers,
> Dale
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/