From: Matt Bentley (mattdbentley@gmail.com)
Date: Sat Jun 21 2008 - 21:47:38 ART
Hi John:
So, from what I can tell, you are trying to reinject 150.1.7.0 from the
aggregate 150.1.0.0/20. I am assuming you are using IE workbooks - or at
least a similar format, - so I am assuming 150.1.8.8 is SW2's loop, etc.,
1. You are trying to reinject 150.1.7.0 from the aggregate 150.1.0.0/20
2. SW2 originally aggregated the prefix, but R6 is peering with R3
Here is how you'd get that prefix to show up on R6.
R6:
router bgp zz
bgp inject-map INJECTED_PREFIX exist-map PEERING_AGGREGATE
route-map INJECTED_PREFIX
set ip add pref INJECTED_PREFIX
route-map PEERING_AGGREGATE
match ip route-source prefix-list PEERING
match ip add prefix-list AGGREGATE
ip prefix-list INJECTED_PREFIX seq 5 permit 150.1.7.0/24
ip prefix-list PEERING seq 5 permit 150.1.3.3/32
ip prefix-list AGGREGATE seq 5 permit 150.1.0.0/20
HTH
On Sat, Jun 21, 2008 at 7:44 PM, John <jgarrison1@austin.rr.com> wrote:
> So from the following information the bgp peer add is 150.1.3.3/32correct?
>
>
> 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
>>>
>>>
> ----- Original Message ----- From: "Matt Bentley" <mattdbentley@gmail.com>
> To: "John" <jgarrison1@austin.rr.com>
> Cc: <ccielab@groupstudy.com>
> Sent: Saturday, June 21, 2008 5:08 PM
> Subject: Re: BGP inject map
>
>
>
> 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
>>>
>>
>>
>> _______________________________________________________________________
>> 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