[nsp] bgp - aggregates and specific routes

[Tantsura, Jeff]

Roger,

But again, you'll have to advertise /24 to your upstreams(deaggregate).
Otherwise your network will never be a downstream to the customer,
traffic will follow the longest prefix
ie /24 from other upstreams vs /19 from you.

So the config will be:

neighbor <IP> unsuppress-map LONGER_PREFIX

ip prefix-list LONGER_PREFIX seq 5 permit </24>

route-map LONGER_PREFIX permit 10
 description Use for unsuppress longer prefix to a bgp neighbor
 match ip address prefix-list LONGER_PREFIX


Jeff


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Roger
Sent: Wednesday, July 14, 2004 10:02 PM
To: cisco-nsp at puck.nether.net
Subject: Re: [nsp] bgp - aggregates and specific routes

james edwards wrote:

>You can disagree, but routing cares less what you think !
>
> 
>
James - I was not disagreeing w/ the fact that yes a /24 will be taken
over a /19..  I was under the impression I needed to send a negative
announcement for the /24.  I did mention I didn't see the forest for the
trees...

>The customer is multihomed ? So if this /24 is withdrawn as you no
>longer hear it and then advertise it, this /24 announcement advertised
>via the customers other transit connection will become preferred. It
>will overrule your aggregate announcement. Always.
>
> 
>
Yes they are multihomed - the downstream customer will eventually have 3
eBGP connections..


--
Rock River Internet                          Roger Grunkemeyer
202 W. State St, 8th Floor                grunky at rockriver.net
Rockford, IL 61101                           815-968-9888 x102

_______________________________________________
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/




Our name has changed.  Please update your address book to the following format: "recipient at capgemini.com".

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.