From: Matt Bentley (mattdbentley@gmail.com)
Date: Sat Jun 21 2008 - 20:08:26 ART
The BGP inject map exist route-map has two components.
route-map inject
set ip add pref PREF
route-map exist
match ip add route-source prefix-list PEERING_ADD
match ip add pref AGGREGATE
ip prefix-list PEERING_ADD seq 5 permit x.x.x.x/32
ip prefix-list AGGREGATE seq 5 permit y.y.y.y/z
ip prefix-list PREF seq 5 permit t.t.t.t/q
Peering address is exactly as you type it in under the BGP process
Aggregate is as it appears in BGP table
HTH
On Sat, Jun 21, 2008 at 6:13 PM, John <jgarrison1@austin.rr.com> wrote:
> I can not figure out what I'm doing wrong. The only thing I can think of
> is
> the route source. I've tried 150.1.3.3 the neighbor the route is coming
> from
> and 167.1.58.8 which is the source of the aggregate route. I'm being
> obtuse
> any help would be greatly appreciated. The config is as follows.
>
> bgp inject-map inject exist-map exist
>
> route-map inject permit 10
> set ip address prefix-list sw1lo0
>
> route-map exist permit 10
> match ip address prefix-list routesource agg
>
> ip prefix-list agg seq 5 permit 150.1.0.0/20
> !
> ip prefix-list routesource seq 5 permit 167.1.58.8/32
> !
> ip prefix-list sw1lo0 seq 5 permit 150.1.7.0/24
>
> R6(config)#do sh ip bgp 150.1.0.0
> BGP routing table entry for 150.1.0.0/20, version 12
> Paths: (1 available, best #1, table Default-IP-Routing-Table)
> Advertised to update-groups:
> 2 3
> 65078, (aggregated by 65078 150.1.8.8)
> 167.1.58.8 (metric 2716160) from 150.1.3.3 (150.1.3.3)
> Origin IGP, metric 0, localpref 100, valid, internal,
> atomic-aggregate,
> best
> Originator: 150.1.5.5, Cluster list: 150.1.3.3
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:22 ART