Re[2]: BGP advertise-map non-exist-map

From: badger (badger@pongo.org)
Date: Sat Jun 14 2003 - 15:50:01 GMT-3


Hello R&S,

Saturday, June 14, 2003, 10:42:16 AM, you wrote:

RSG> try creating route-maps called LIST and TRACK, not extended access-lists
RSG> eg
RSG> route-map LIST permit 10
RSG> match ip address 10
RSG> !
RSG> accerss-list 10 permit 192.168.1.0 0.0.0.255

RSG> Adam

>> ----------
>> From: badger
>> Reply To: badger
>> Sent: Saturday, June 14, 2003 5:05 PM
>> To: ccielab@groupstudy.com
>> 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
>>

Nope, this didn't fix it.

-- 
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