[j-nsp] Multicast design with PIM-SM

[Guy Davies]

I think that you wouldn't lose the locally connected sources even if
the connection was still to the RPT.

When the IGMP membership report was received on the router for (*,G)
the router already has the (S,G) and (*,G) for the locally sourced
content with an iif from the source and an oif towards the RP.  IIUC,
a new oif would be added for the interface on which the IGMP
membership report was received.

Rgds,

Guy

On 14/02/06, Chuck Anderson <cra at wpi.edu> wrote:
> On Tue, Feb 14, 2006 at 04:32:34PM +0100, F J wrote:
> > When the link between the two routers go down I assume the clients will
> > loose ALL multicast groups since the non-RP router looses contact with the
> > RP. I would like them to still be able to see the groups that belong to the
> > multicast sources connected to the non-RP router...
>
> If the multicast streams have switched over to the Shortest Path Tree,
> then this should not be the case.
>
> > Any suggestions how this could be achieved in an easy way?
>
> Set up both routers as RPs for the same group ranges and enable MSDP
> in a mesh group between them.
>
> msdp {
>     rib-group inet mcast-rpf-rib;
>     active-source-limit {
>         maximum 20000;
>         threshold 15000;
>     }
>     export msdp-import-filter;
>     import msdp-import-filter;
>     group CORE {
>         mode mesh-group;
>         local-address my.ip.address;
>         peer other.ip.address;
>     }
> }
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>