From: Connie Nie (CNie@EPLUS.com)
Date: Sun Jun 15 2003 - 19:44:04 GMT-3
Badger,
There is a known issue with BGP conditional advertisement--I ran into that
myself a few weeks ago. Search the bug list you will find the version that
is affected.
Connie
-----Original Message-----
From: badger [mailto:badger@pongo.org]
Sent: Saturday, June 14, 2003 1:54 PM
To: Mustafa M Bayramov
Cc: ccielab@groupstudy.com
Subject: Re[2]: BGP advertise-map non-exist-map
Hello Mustafa,
Saturday, June 14, 2003, 11:32:16 AM, you wrote:
MMB> When you removing lo192 on r2 does it disappear on r1?
MMB> I've tested advertise map on 12.1.5T and work correct.
MMB> Regards
MMB> -----Original Message-----
MMB> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
MMB> badger
MMB> Sent: Saturday, June 14, 2003 12:06 PM
MMB> To: ccielab@groupstudy.com
MMB> Subject: BGP advertise-map non-exist-map
MMB> Hello ccielab,
MMB> I'm using 12.1(5)T14 and can't seem to get the neighbor x.x.x.x
MMB> advertise-map non-exist-map to work. I did check the archives and
MMB> found no useful information pertaining to this problem. My
MMB> question... is there a know IOS issue with this, or are my configs
MMB> not correct?
MMB> here are the configs:
MMB> as1 as1
MMB> r1--------r2
MMB> r1
MMB> router bgp 1
MMB> no synchronization
MMB> bgp router-id 1.1.1.1
MMB> bgp log-neighbor-changes
MMB> neighbor 2.2.2.2 remote-as 1
MMB> neighbor 2.2.2.2 update-source Loopback0
MMB> neighbor 2.2.2.2 soft-reconfiguration inbound
MMB> no auto-summary
MMB> -------------
MMB> BGP table:
MMB> Network Next Hop Metric LocPrf Weight Path
*>>i172.16.1.0.0/24 2.2.2.2 0 100 0 i
*>>i172.16.2.0.0/24 2.2.2.2 0 100 0 i
MMB> R2
MMB> interface Loopback191
MMB> ip address 192.168.1.1 255.255.255.0
MMB> interface Loopback192
MMB> ip address 192.168.2.1 255.255.255.0
MMB> shutdown
MMB> interface Loopback171
MMB> ip address 172.16.1.1 255.255.255.0
MMB> interface Loopback200
MMB> ip address 172.16.2.1 255.255.255.0
MMB> router bgp 1
MMB> no synchronization
MMB> bgp router-id 2.2.2.2
MMB> bgp log-neighbor-changes
MMB> network 172.16.1.0
MMB> network 172.16.2.0
MMB> network 192.168.1.0
MMB> network 192.168.2.0
MMB> neighbor 1.1.1.1 remote-as 1
MMB> neighbor 1.1.1.1 update-source Loopback0
MMB> neighbor 1.1.1.1 soft-reconfiguration inbound
MMB> neighbor 1.1.1.1 advertise-map LIST non-exist-map TRACK
MMB> no auto-summary
MMB> ip access-list standard LIST
MMB> permit 192.168.1.0 0.0.0.255
MMB> ip access-list standard TRACK
MMB> permit 192.168.2.0 0.0.0.255
MMB> route-map prime LIST 10
MMB> match ip address LIST
MMB> route-map TRACK permit 10
MMB> match ip address TRACK
MMB> -------------
MMB> BGP table:
MMB> Network Next Hop Metric LocPrf Weight Path
*>> 192.168.1.0 0.0.0.0 0 32768 i
*>> 172.16.1.0 0.0.0.0 0 32768 i
*>> 172.16.2.0 0.0.0.0 0 32768 i
MMB> ------------------
MMB> Interface loop192 is shutdown, so the 192.168.1.0 should be
MMB> advertised to r1, but it isn't making it.
MMB> Thanks for any insight
I tried that too, but it still doesn't get to r1. I've tried
everyones's suggestions and even tried this on different routers with
no luck. ALl my routers are running the same code.
Are you running 12.1(5)T or 12.1(5)T14?
-- Best regards, badger mailto:badger@pongo.org
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:58 GMT-3