Hello,
In a fairly large EX switching environment, we're using IGMP snooping
to constrain some AV-over-IP multicast traffic. It's quite
bandwidth-intensive, so we obviously don't want it broadcasting over
our L2 network.
According to The Rules, multicast traffic gets sent to any subscribed
host interface (learned through a membership report), as well as to
any router interface. This means that our router will see all the
multicast on the subnet, even if none of it needs to be routed. The
link between the L2 network and the router will get saturated with
multicast.
I suppose we could give the router a beefy 40G connection, and use QoS
to handle congestion. But I was hoping to find a way to keep the
multicast pushed down in the EX environment where it actually belongs.
Am I missing something here?
Norman
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
In a fairly large EX switching environment, we're using IGMP snooping
to constrain some AV-over-IP multicast traffic. It's quite
bandwidth-intensive, so we obviously don't want it broadcasting over
our L2 network.
According to The Rules, multicast traffic gets sent to any subscribed
host interface (learned through a membership report), as well as to
any router interface. This means that our router will see all the
multicast on the subnet, even if none of it needs to be routed. The
link between the L2 network and the router will get saturated with
multicast.
I suppose we could give the router a beefy 40G connection, and use QoS
to handle congestion. But I was hoping to find a way to keep the
multicast pushed down in the EX environment where it actually belongs.
Am I missing something here?
Norman
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp