[j-nsp] Multicast senders/receivers on the same PE (different VRF) with NG MVPN

[Vladislav A. VASILEV]

Hi Krasimir,

I had only considered vt interfaces for doing filtering/additional look ups
for traffic egressing L3VPNs (prior to the vrf-table-lable being
available). I now have a working NG MVPN (extranet). However, what if I
wanted to have senders/receivers physically terminated on the same router,
but on different MPCs? Effectively, traffic wouldn't be processed by the
same Trio chip = different vt interface!

Thanks,
Vladi



On Thu, Nov 22, 2012 at 1:54 PM, Krasimir Avramski <krasi at smartcom.bg>wrote:

> Hi,
>
> NG-MVPN extranets are supported since junos 9.5:
>
>
> http://www.juniper.net/techpubs/en_US/junos11.4/topics/topic-map/mcast-mbgp-extranets.html#jd0e120
>
> As I remember in some corner cases(only two extranet VRFs on the same
> router - if my memory serves me right) there is NO need for tunnel hw (VT-
> ifls)  -  only  "vrf-table-label" (lsi ifls) should do the trick.
>
> Best Regards,
> Krasi
>
> On Thu, Nov 22, 2012 at 2:54 PM, Vladislav A. VASILEV <
> vladislavavasilev at gmail.com> wrote:
>
>> Hi all,
>>
>> I need to deliver multicast data to a receiver in a VRF, which resides on
>> the same PE as the sender VRF.
>>
>> The only way I see this could be done is by putting one of the VRFs into a
>> logical system and presenting the traffic over an lt interface. The
>> problem
>> is that this type of design does not scale. What if down the road I had
>> another customer which wanted to receive multicast data from both the
>> current sender/receiver? I'd then need to put it into another logical
>> system (basically introducing another PE, being a logical one)?
>>
>> What options do I have?
>>
>> Thanks,
>> Vladi
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>