![]() ![]()
welisson_br
Created Nov 12, 2019 14:29:08
Hi Chenhui, Yep I have almost 2k multicast users connected on this switch. I really haven't found any place informed about the real limit this switch about multicast stream. have you? Cheers |
![]() ![]()
welisson_br
Created Nov 10, 2019 15:16:45
Hi DDSN, I've already done it as you can see below; cpu-defend policy igmpdefend car packet-type igmp cir 512 auto-port-defend protocol igmp threshold 256 >dis cu | include cpu-defen cpu-defend policy igmpdefend cpu-defend-policy igmpdefend global Although doing that the issues still persist. Cheers, |
![]() ![]()
welisson_br
Created Nov 11, 2019 21:07:20
Hi Chenhui. Actually not, in this case that massive igmp/leave is caused by clients wich are getting in/out on the multicast group. |
![]() ![]()
welisson_br
Created Nov 12, 2019 14:29:08
Hi Chenhui, Yep I have almost 2k multicast users connected on this switch. I really haven't found any place informed about the real limit this switch about multicast stream. have you? Cheers |
![]() ![]()
welisson_br
Created Nov 12, 2019 14:55:03
I did that configuration on CPCAR, and auto-defend, including set up whitelist with my range ip address allowed to make igmp query/join/report and so on, but not successful. So, increasing igmp values on cpcar more than 256 the switchs starts working not so good, where the access become quite slowly and the latency ahead it. is quite high as well, for sure the cpu get over 50% having peaks 80% when increased the cpcar over 256. I'm wondering is this switch can deal with a large multicast flow? |
|
|
|