From: Ravi Singh (way2ccie@googlemail.com)
Date: Tue Feb 17 2009 - 21:42:22 ARST
Sadiq,
I think what you are talking about here is the use of an inject-map with an
exist/non-exist-map. However, for Mahesh's question he is using an
advertise-map.
Mahesh,
The network 136.1.23.0/24 needs to be in the BGP table and not in the
routing table. I think it does not exist in the BGP table which makes the
condition of the "non-exist-map" to true and the route 136.1.29.0/24 is
being advertised.
HTH
Ravi
On Tue, Feb 17, 2009 at 10:41 PM, Sadiq Yakasai <sadiqtanko@gmail.com>wrote:
> I havent done this in a long time, but i remember 2 things which I havent
> see above:
>
> 1. There was matching on the "next-hop" of a prefix. I dont remember if
> this
> goes in the first or second route-map. Check that one.
>
> 2. The route-map containing the prefix to be injected should have "set ip
> address" and not "match ip add". Can you check this feature documentation
> again to confirm these things please?
>
> HTH,
>
> Sadiq
>
> On Tue, Feb 17, 2009 at 10:23 PM, Mahesh Shivaswamy <
> maheshs.cisco@gmail.com
> > wrote:
>
> > Hi,
> >
> > I am not sure why is R2 advertising prefix 136.1.29.0/24 when the
> > route 136.1.23.0/24 exist in the routing table ???
> >
> > I have the following configs on R2
> >
> > R2#sh run | be router bgp
> > router bgp 300
> > no synchronization
> > bgp router-id 150.1.2.2
> > bgp log-neighbor-changes
> > network 136.1.29.0 mask 255.255.255.0
> > neighbor 136.1.23.3 remote-as 100
> > neighbor 136.1.29.9 remote-as 100
> > neighbor 136.1.245.5 remote-as 200
> > neighbor 136.1.245.5 advertise-map ADVERTISE non-exist-map NON-EXIST
> > no auto-summary
> > !
> > ip prefix-list HDLC seq 5 permit 136.1.23.0/24
> > !
> > ip prefix-list VLAN29 seq 5 permit 136.1.29.0/24
> > !
> > route-map NON-EXIST permit 10
> > match ip address prefix-list HDLC
> > !
> > route-map ADVERTISE permit 10
> > match ip address prefix-list VLAN29
> >
> > R2#sh ip bgp ne 136.1.245.5 advertised-routes
> > BGP table version is 9, local router ID is 150.1.2.2
> > Status codes: s suppressed, d damped, h history, * valid, > best, i -
> > internal,
> > r RIB-failure, S Stale
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> > *> 136.1.3.0/24 136.1.23.3 0 0 100 i
> > *> 136.1.29.0/24 0.0.0.0 0 32768 i
> >
> > Total number of prefixes 2
> >
> >
> > R2#sh ip bgp ne 136.1.245.5 | in Condition
> > Condition-map NON-EXIST, Advertise-map ADVERTISE, status: Advertise
> >
> >
> > R2#sh ip route 136.1.23.0
> > Routing entry for 136.1.23.0/24
> > Known via "connected", distance 0, metric 0 (connected, via interface)
> > Redistributing via ospf 1, eigrp 100
> > Advertised by ospf 1
> > Routing Descriptor Blocks:
> > * directly connected, via Serial0/1
> > Route metric is 0, traffic share count is 1
> >
> > rgds
> > Mahesh
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> CCIE #19963
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:11 ARST