[j-nsp] NG-MVPN RPT-SPT mode no receiver CE limitation?

[Krasimir Avramski]

I have had customer using exactly the same setup (in production) without
any problems on receiver PE (static igmp local receivers for faster channel
zapping). Now I can't remember if igmp was effectively filtered on
downstream access equipment. The problem with local receivers was only on
Source PE ( if you have type-7 C-M route then Source PE local receivers
would stop receive mcast traffic - 9.6 release, DPC hardware). The work
around was to deploy another vrf on source PE to terminate local receivers
and source mcast interface and mvpn vrf serving only remote PEs). On 11.2
it was dependent on type of hardware used(MPC, DPC) for interfaces
connecting multicast source, mpls core and local receivers - for example if
DPC hardware was used for ifls connecting mcast source, mpls core and local
receivers then it was OK - every other combination (including only MPC
hardware) affected local source PE receivers or remote PEs not receiving
multicast traffic at all.
I really don't know current state with latest software/hardware, but rather
you are hitting some bug.

Best Regards,
Krasi


On 27 May 2014 14:13, Vladislav A. VASILEV <vladislavavasilev at gmail.com>wrote:

> Does anybody know if this limitation still exist:
>
> Source CE --- Source PE --- MPLS Network --- Receiver PE --- Static IGMP
> under VRF interface (no Receiver CE)
>
> It works but the problem is that for no reason multicast traffic would stop
> flowing (within a few days) due to BGP withdrawing all route types (except
> neighbour discovery). Deactivating/activating the routing instance under
> the receiver PE solves the problem for a few days and it would then happen
> again. I've had a JTAC case opened for a few weeks now, but I still have
> not been given a clear answer as to whether or not this is supported.
>
> Thanks,
> Vladi
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>