[c-nsp] Interesting Problem - MPBGP Filtering

[David Freedman]

Not sure if this is helpful, but have you seen this?

http://www.cisco.com/en/US/products/ps6604/products_white_paper0900aecd80581f3d.shtml

For your PE routers running SXF I think (if I'm reading correctly) that 
you dont implement an SAFI for MDT, you simply use an extcommunity

12.2SR implements this an seperate SAFI

It could be this which is the cause somehow, it mentions the following 
warning:

"
There are two basic issues with this approach, use of RD Type 2 is not 
standard, and the BGP attribute is non-transitive, and cannot work for 
Inter-AS MVPN. In "BGP/MPLS IP VPNs" (RFC4364), RD Type 2 is designated 
for the representation of 4 byte AS numbers (RFC4893). This overlap in 
usage can cause collisions between the RD Type 2 MVPN MDT advertisement 
and a unicast VPNv4 advertisement using RD Type 2 for encoding the 4 
byte AS number.
"

Can't think of much else.

Dave.


Marko Milivojevic wrote:
> That was my thinking exactly - but the problem is that multicast routing is not enabled on R1 and it doesn't have any MVPN configuration. Like I said in my original e-mail - it's not a major problem, but I would just like to understand why am I seeing what I'm seeing :-)
> 
> 
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Peter Rathlev
> Sent: 12. nóvember 2007 13:11
> To: cisco-nsp
> Subject: Re: [c-nsp] Interesting Problem - MPBGP Filtering
> 
> Marko Milivojevic wrote:
> <snip>
>> BGP routing table entry for 2:AS:4:PE.PE.PE.225/32, version 67
>> Paths: (2 available, best #2, no table, not advertised to EBGP peer)
>>   Not advertised to any peer
>>   Local
>>     PE.PE.PE.225 (metric 101) from PE.PE.PE.226 (PE.PE.PE.226)
>>       Origin incomplete, metric 0, localpref 100, valid, internal,
>> mdt, no-import
>>       Extended Community: RT:AS:4 MDT:AS:239.232.4.1
>>       Originator: PE.PE.PE.225, Cluster list: 0.0.0.1
>>       mpls labels in/out nolabel/3
>>   Local
>>     PE.PE.PE.225 (metric 101) from PE.PE.PE.225 (PE.PE.PE.225)
>>       Origin incomplete, metric 0, localpref 100, valid, internal,
>> mdt, no-import, best
>>       Extended Community: RT:AS:4 MDT:AS:239.232.4.1
>>       mpls labels in/out nolabel/3
> <snip>
> 
> I know next to nothing about MVPN, but maybe there's a connection 
> between your unwanted prefixes and the "mdt" and "no-import" attributes.
> Maybe you simply can't filter out the PE-nodes in the MDT, as long as R1
> is part of the MVPN network.
> 
> So maybe "no" is the answer, you can't get rid of them. Just a guess
> though, I have no clue, and I should probably just keep quiet... :-)
> 
> Regards,
> Peter Rathlev
> 
> 
> _______________________________________________
> 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/
> _______________________________________________
> 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/
>