From: Mahesh Shivaswamy (maheshs.cisco@gmail.com)
Date: Wed Feb 18 2009 - 16:24:34 ARST
Ravi, Dale, Narbik, Braychuck,
Thanks all for your reply, I had not advertised the HDLC link to BGP,
hence the problem....once I advertised this everything works as
expected.......Thanks a ton again for your time....
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.23.0 mask 255.255.255.0
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
R2#sh ip bgp nei 136.1.245.5 advertised-routes
BGP table version is 11, 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.23.0/24 0.0.0.0 0 32768 i
Total number of prefixes 2
R2#sh ip bgp nei 136.1.245.5 | in Condition
Condition-map NON-EXIST, Advertise-map ADVERTISE, status: Withdraw
-Mahesh
On 2/18/09, Salahaddin Elshekeil <salah.elshekeil@gmail.com> wrote:
> this is in the lab 3 vol 2 I think
>
>
>
>
>
> The idea is to forse R5 to route through R1 to reach 136.1.29.0/24,
>
>
>
> in case the connection between R2---R3 lost R2 will advertise
> 136.1.29.0/24to R5 then R5 will route directly to R2 through
> frame-relay
>
>
>
> There is no way to force R5 to route through R1 because in the previous
> task
> u already configured weight 100 to 136.1.29.0/24
>
>
>
> this is what I understood :)
>
>
>
> HTH
>
>
>
> Salah
>
>
>
>
> On Wed, Feb 18, 2009 at 4:23 PM, Braychuck Vitaliy <
> Vitaliy.Braychuck@incom.ua> wrote:
>
>> You have confused conditional advertisement with conditional injection,
>> man
>> ;)
>>
>> -----Original Message-----
>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>> Sadiq Yakasai
>> Sent: Wednesday, February 18, 2009 12:42 AM
>> To: Mahesh Shivaswamy
>> Cc: Cisco certification
>> Subject: Re: BGP conditional advertise not working.
>>
>> 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
>>
>> _______________________________________________________________________
>> 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