From: Ben (ccieben@cox.net)
Date: Mon Feb 12 2007 - 13:52:00 ART
Hi Dishan,
How are you applying the route-map on PE1? Mocking up your scenario, I
had good luck with your configurations in setting the route-map on the
PE1 neighbor statement to RR:
neighbor <RR-IP> route-map dishan in
You would not want to send-community (though it shouldn't hurt) or set
the community egress towards CPE2.
HTH
Ben
Dishan Gamage wrote:
> Hi Group
>
>
> The setup is as follows
>
>
> CPE1<----->ebgp<---->-PE2<--ibgp-->-RR<---->-PE1 <---ebgp----> CPE2
>
> CPE1 in AS 100 (directly connected to PE2)
>
> PE1,PE2, RR in AS 65001
>
> CPE2 in AS 200 (directly connected to PE1)
>
>
> I need to configure in PE1 to block new routes from being advertised to AS
> 200 (ie CPE2) from AS100 (CPE1)
>
> I tried the following on PE1
>
> ip prefix-list BB1 seq 10 permit 20.1.1.0/24
> ip prefix-list BB1 seq 15 permit 5.5.5.0/24
>
> route-map dishan permit 10
> match ip address prefix-list BB1
> !
> route-map dishan permit 20
> set community no-export
>
> on CPE2, the 20.1.1.0 & 5.5.5.0 were seen, but also along with the rest of
> the routes with the community no-export taged !!!
>
>
> How can i correct this please?? I don't want any new routes to go to AS200
>
> I can only configure PE1
>
> Tks in advance
>
> Dishan
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Thu Mar 01 2007 - 07:38:46 ART