I am still doing something wrong. Below is my new configuration, this
router is learning this route from an iBGP neighbor, but when I look at the
eBGP neighbor peered to this router I see the 33.33.33.0/24 route, but not
the 33.33.33.33/32 route. Does anyone see anything wrong with this? I did
a clear ip bgp * and still the same...
Thanks,
router bgp 100
no synchronization
bgp log-neighbor-changes
bgp inject-map ORIGINATE exist-map LEARNED copy-attributes
network 11.11.11.0 mask 255.255.255.0
neighbor 24.234.2.2 remote-as 200
neighbor 24.234.2.2 ebgp-multihop 255
neighbor 24.234.2.2 update-source Loopback0
neighbor 24.234.3.3 remote-as 100
neighbor 24.234.3.3 update-source Loopback0
no auto-summary
!
!
!
ip prefix-list HOST seq 5 permit 33.33.33.33/32
!
ip prefix-list ROUTE seq 5 permit 33.33.33.0/24
!
ip prefix-list SOURCE seq 5 permit 24.234.3.3/32
!
!
!
route-map ORIGINATE permit 10
match ip address prefix-list HOST
!
route-map LEARNED permit 10
match ip address prefix-list ROUTE
match ip route-source prefix-list SOURCE
!
On Sun, Oct 17, 2010 at 7:14 PM, garry baker <baker.garry_at_gmail.com> wrote:
> you need the *match ip route-source* in your route-map EXISTS*
>
> *
>
http://www.cisco.com/en/US/docs/ios/iproute_bgp/configuration/guide/irg_basic
_net_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1055919
>
> Specifies the match conditions for redistributing the source of the route.
>
> In this example, the prefix list named ROUTE_SOURCE is used to
> redistribute the source of the route.
>
> *Note *The route source is the neighbor address that is configured with
> the *neighbor remote-as* command. The tracked prefix must come from this
> neighbor in order for conditional route injection to occur.
>
>
> --
> Garry L. Baker
>
> "There is no 'patch' for stupidity." - www.sqlsecurity.com
>
>
> On Sun, Oct 17, 2010 at 5:12 PM, Steven Blasiol
<steven.blasiol_at_gmail.com>wrote:
>
>> Experts,
>>
>> I am having some problems with an inject map and would appreciate some
>> help:
>>
>> router bgp 23
>> no synchronization
>> bgp log-neighbor-changes
>> bgp inject-map INJECT exist-map EXISTS copy-attributes
>> network 24.234.32.0 mask 255.255.255.0
>> aggregate-address 24.0.0.0 255.0.0.0 summary-only
>> redistribute ospf 1 route-map OSPF
>> neighbor 155.60.1.1 remote-as 10
>> neighbor 155.60.1.1 ebgp-multihop 255
>> neighbor 155.60.1.1 update-source Loopback0
>> neighbor 155.60.1.1 weight 3000
>> neighbor 155.60.3.3 remote-as 23
>> neighbor 155.60.3.3 update-source Loopback0
>> neighbor 155.60.3.3 next-hop-self
>> neighbor 155.60.3.3 route-map LOCALPREF in
>> no auto-summary
>> !
>> ip prefix-list EXISTS seq 5 permit 33.33.33.0/24
>> !
>> ip prefix-list INJECT seq 5 permit 33.33.33.33/32
>> !
>> route-map EXISTS permit 10
>> match ip address prefix-list EXISTS
>> !
>> route-map INJECT permit 10
>> set ip address prefix-list INJECT
>>
>> When I look at routers that are peered to this router I can see
>> 33.33.33.0/24 (33.33.33.33 is a loopback on this router) but I do not see
>> the 33.33.33.33/32
>>
>> Thanks
>>
>>
>>
>>
>>
>> --
>> Steven M. Blasiol
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>
-- Steven M. Blasiol Blogs and organic groups at http://www.ccie.netReceived on Sun Oct 17 2010 - 21:09:57 ART
This archive was generated by hypermail 2.2.0 : Mon Nov 01 2010 - 06:42:06 ART