From: Chad Hintz (ccie_2b2004@yahoo.com)
Date: Tue Nov 15 2005 - 02:19:19 GMT-3
Daniel,
I would create a prefix list permiting only the summary, I know you said this was not scalable but with sequence numbers it is. Since you need to add additional routes you can create a seq number higher than the original (by default is 5).
So for additional routes you only need to create another line in the prefix for each route. You can also think of it in the other fashion by using a prefix list to deny the routes from bb3 except the summary and create a permit 0.0.0.0/0 le 32 line to permit all other traffic.
HTH,
Chad
Paresh Khatri <Paresh.Khatri@aapt.com.au> wrote:
Hi Daniel,
Why don't you use an inbound route-map (on the session with the Backbone router) with a prefix-list to match on all longer prefixes of the aggregate and tag them with a 'no-advertise' community ?
Paresh.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Daniel Berlinski
Sent: Tuesday, 15 November 2005 02:00 PM
To: ccielab@groupstudy.com
Subject: BGP question
Hi
Please consider the following scenario:
Backbone --- R3 --- R1
I'm summarizing incoming routes from Backbone in R3. I need to see in R1 only the summary route. I'm not permitted to use unsuppress-map or summary-only keyword with aggregate-address in R3. My solution needs to be flexible with future additional routes coming from backbone:
I've tried different things (unsuppress maps and prefix-list which is not very scalable) and now I'm feeling totally out of track. Would not like to be given the straight answer but just a hint to put me in the right direction would help in this one.
Cheers
This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3