From: Dino (air@xxxxxxxxxx)
Date: Fri Oct 06 2000 - 23:04:51 GMT-3
Hi Julie,
What I found with this example was that RTC didn't get the aggregate of
192.68.0.0 nor the more specific 192.168.10.0 because of the
filter-list.
When I took out that line it worked just fine. RTC was seeing the
aggregate and 192.68.10.0.
Thanks,
Dino
Connary, Julie Ann wrote:
>
> Hi,
>
> has anyone tried to do the example in Halabi on page 364. Whenever I add
> the adverise-map onto
> my aggregate-address command I loose the aggregate address. Here's my
> config (directly copied from Halabi.)
> I was unable to find other examples on the cisco.com for advertise-map.
>
> router bgp 3
> no synchronization
> network 172.16.1.0 mask 255.255.255.0
> network 172.16.10.0 mask 255.255.255.0
> network 172.16.65.0 mask 255.255.255.192
> network 172.16.220.0 mask 255.255.255.0
> aggregate-address 192.68.0.0 255.255.0.0 as-set advertise-map select
> neighbor 172.16.1.2 remote-as 3
> neighbor 172.16.1.2 update-source Loopback0
> neighbor 172.16.20.1 remote-as 1
> neighbor 172.16.20.1 filter-list 10 out
> neighbor 172.16.220.2 remote-as 5
> !
> ip classless
> ip as-path access-list 10 permit ^$
> !
> access-list 1 permit 192.68.10.0 0.0.0.255
> route-map select permit 10
> match ip address 1
>
> thanks, Julie Ann
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:24 GMT-3