[c-nsp] Interesting Problem - MPBGP Filtering

[Marko Milivojevic]

I think you could be misreading. Entry below is /19 summary - and yes, I want to receive this one with RD AS:1. However, problem are those other /32 entries that do not have AS:1 route-target atached - hence, they should be filtered out.

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of David Freedman
Sent: 12. nóvember 2007 12:36
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Interesting Problem - MPBGP Filtering




Marko Milivojevic wrote:
> Sure thing.
> 
> PE1 - PE.PE.PE.225
> PE2 - PE.PE.PE.226
> 
> R1#sh ip bgp vpn all PE.PE.PE.225
> BGP routing table entry for AS:1:X.X.X.X.0/19, version 57
> Paths: (2 available, best #1, table Internet)
>   Not advertised to any peer
>   Local
>     PE.PE.PE.225 (metric 101) from PE.PE.PE.225 (PE.PE.PE.225)
>       Origin IGP, metric 0, localpref 1000, valid, internal, best
>       Community: AS:0
>       Extended Community: RT:AS:1
>       mpls labels in/out nolabel/55

<snip>

Well, this is your problem then, you are tagging your PE /32s
with extcommunity AS:1 and standard community AS:0,
the combination of which are permitted in the first entry
of your route-map.

!
ip extcommunity-list standard AS-Internet permit rt AS:1
ip community-list standard AS-Originated-Routes permit AS:0
!
route-map PE-in permit 5
!
  match extcommunity AS-Internet
  match community AS-Originated-Routes
!

Unless I'm misreading this?

Dave.


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/