[c-nsp] route-target import on non-leaking PEs

[Christian Meutes]

You need add-path on both sides, yes. But as Phil already noted your RRs are definitely tie-breaking to different pathes. 

On 13.12.2012, at 22:12, Phil Mayers <p.mayers at imperial.ac.uk> wrote:

> On 13/12/12 15:04, Jason Lixfeld wrote:
>> 
>> On 2012-12-13, at 9:56 AM, Phil Mayers <p.mayers at imperial.ac.uk>
>> wrote:
>> 
>>> On 13/12/12 14:47, Jason Lixfeld wrote:
>>>>> 
>>>>> Yes. In fact, that's *required* if you want to do multi-path.
>>>> 
>>>> I seem to do multi-path just fine with maximum-paths ibgp 2 on my
>>>> RR clients inside a VRF that sees a default sourced from two
>>>> different RRs.  Said VRF has a common RD between the two PEs.
>>>> 
>>>> How is that different?
>>> 
>>> Well, AIUI multipath *ought* to require unique RDs. Obviously not;
>>> I wonder how that's working for you?
>> 
>> So based on the link you posted previously, which I am currently
>> making my way through, what's happening is on my production network
>> where this multi-path stuff is actually working, I'm using XR as my
>> RRs, which has add-path support.
> 
> Presumably the RR clients have add-path too (it's needed at both ends)?
> 
> Other explanations might be that by chance one RR had advertised one path and the other RR another path.
> 
> But yes, my original email should have been more specific: unless you have add-paths, unique RD is required for multipath.
> _______________________________________________
> 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/