From: badger (badger@pongo.org)
Date: Sat Jun 14 2003 - 15:49:33 GMT-3
Hello Daniel,
Saturday, June 14, 2003, 10:55:28 AM, you wrote:
DF> Hi,
DF> Taking a guess but:
>> route-map prime LIST 10
>> match ip address LIST
DF> I think the route-map name should be:
DF> route-map LIST 10
DF> !!!!!!!!!
DF> Also I am a bit confused with your BGP network
DF> statements. Unless with Ver 12.1 the class doesn't matter but I thought if
DF> you have a interface like Loopback 171 - IP 172.16.1.1 255.255.255.0 then
DF> under BGP you would need to say:
DF> router bgp 1
DF> network 172.16.1.0 mask 255.255.255.0
DF> !!!!!
DF> Since it is suppose to match exactly what is in your
DF> routing table. Apparently looking at your config this
DF> is not the case. Any feeback from forum is appreciated.
DF> Danny
DF> ----- Original Message -----
DF> From: "badger" <badger@pongo.org>
DF> To: <ccielab@groupstudy.com>
DF> Sent: Saturday, June 14, 2003 12:05 PM
DF> Subject: BGP advertise-map non-exist-map
>> Hello ccielab,
>>
>> I'm using 12.1(5)T14 and can't seem to get the neighbor x.x.x.x
>> advertise-map non-exist-map to work. I did check the archives and
>> found no useful information pertaining to this problem. My
>> question... is there a know IOS issue with this, or are my configs
>> not correct?
>>
>> here are the configs:
>>
>> as1 as1
>> r1--------r2
>>
>> r1
>> router bgp 1
>> no synchronization
>> bgp router-id 1.1.1.1
>> bgp log-neighbor-changes
>> neighbor 2.2.2.2 remote-as 1
>> neighbor 2.2.2.2 update-source Loopback0
>> neighbor 2.2.2.2 soft-reconfiguration inbound
>> no auto-summary
>> -------------
>> BGP table:
>> 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
>>
>> R2
>>
>> interface Loopback191
>> ip address 192.168.1.1 255.255.255.0
>> interface Loopback192
>> ip address 192.168.2.1 255.255.255.0
>> shutdown
>> interface Loopback171
>> ip address 172.16.1.1 255.255.255.0
>> interface Loopback200
>> ip address 172.16.2.1 255.255.255.0
>>
>> router bgp 1
>> no synchronization
>> bgp router-id 2.2.2.2
>> bgp log-neighbor-changes
>> network 172.16.1.0
>> network 172.16.2.0
>> network 192.168.1.0
>> network 192.168.2.0
>> neighbor 1.1.1.1 remote-as 1
>> neighbor 1.1.1.1 update-source Loopback0
>> neighbor 1.1.1.1 soft-reconfiguration inbound
>> neighbor 1.1.1.1 advertise-map LIST non-exist-map TRACK
>> no auto-summary
>>
>> ip access-list standard LIST
>> permit 192.168.1.0 0.0.0.255
>>
>> ip access-list standard TRACK
>> permit 192.168.2.0 0.0.0.255
>>
>> route-map prime LIST 10
>> match ip address LIST
>>
>> route-map TRACK permit 10
>> match ip address TRACK
>> -------------
>> BGP table:
>>
>> 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
>>
>> ------------------
>>
>> Interface loop192 is shutdown, so the 192.168.1.0 should be
>> advertised to r1, but it isn't making it.
>>
>> Thanks for any insight
>>
>> --
>> Best regards,
>> badger mailto:badger@pongo.org
Thanks for pinting out the route-map mistake, it came from many
variations of trying to get this to work... but this didn't fix the
problem.
I noticed the network statement issue as well and thought it strange
too. However, it seems that if for example I places "network
207.113.50.0 mask 255.255.255.0" into bgp, then after a "sho run" it
truncates the "mask 255.255.255.0" and only displays the "network
207.113.50.0" As an experiment I placed "network 90.90.90.0 mask
255.255.255.0" into bgp and it actually shows in the config as
"network 90.90.90.0 mask 255.255.255.0" I checked this on some of my
other routers and get the same behavior - all running 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