All things related to multicast

[Hank Nussbacher <>]

At 11:57 AM 24-02-08 +0200, Pekka Savola wrote:
> On Sun, 24 Feb 2008, Hank Nussbacher wrote:
> > We have filters in place but they didn't help :-(
> ...
> > ip access-list standard boundary-filter
>
> Your ACL doesn't match sap.mcast.net.  (But if you filter it out 
> completely, your users can't watch places all over the world.) 
> Rate-limiting would be a better option.
>
> > On our msdp router (mcast) which seemed to fair better based
> > on the CPU graphs
> > http://noc.ilan.net.il/stats/ILAN-CPU/mcast-cpu.html:
> >
> > ip multicast boundary boundary-filter
> > ip multicast rate-limit in 40000
> > ip multicast rate-limit out 40000
> > ip igmp access-group igmp-join-filter
> > ip igmp limit 1000
>
> This is more resilient because you have ip multicast rate-limit here, 
> which you didn't have on your core router.
>
> On the other hand, legitimate multicast traffic (e.g. if you'd have IPTV) 
> could trigger rate-limiting with values above.

We've turned off sap listen on the 2 core routers and left it on on the 
msdp router which fared better with the multicast rate-limit.  Now to wait 
for the next SDP spike :-)

-Hank


> Pekka