[c-nsp] Multicast clarification

[Arie Vayner (avayner)]

Martin,

If the 2nd router should never get this mcast traffic, then you can
treat that port as a boundary... I would just put an ACL on it to block
the unwanted multicast groups...
Also, on the router you can block these specific multicast groups.

I think you can find some clues here:
http://www.cisco.mn/en/US/prod/collateral/iosswrel/ps6537/ps6552/ps6592/
whitepaper_c11-474791.html


Arie

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Martin Barry
Sent: Friday, May 07, 2010 17:19
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Multicast clarification

$quoted_author = "Arie Vayner (avayner)" ;
> 
> Without this functionality the routers would not be able to detect new
> sources as the switch would not replicate the stream, and we would
never
> know about this source.

Understood.

But in our situation this VLAN is just a multicast traffic sink, it is
not
retransmitted.

There are two routers because there are multiple sources of multicast
traffic.

 
> If both routers are talking PIM between them then only one of the them
> would be the DR (Designated Router), and only this router would be
> forwarding packets received on this LAN domain.

We are using PIM neighbour filtering to prevent the routers associating
because they are handling different multicast traffic.

This is why my question focused on the 3750 stack. It seems that it's
forwarding multicast out all mrouter ports except the ingress and I was
wondering if there is a way to prevent this as router B never needs to
see
router A's multicast streams.

cheers
Marty
_______________________________________________
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/