[c-nsp] 3850 / 3650 storm control

[Charles Sprickman]

Just chiming in with a quick question...

> On Nov 22, 2017, at 1:25 PM, Saku Ytti <saku at ytti.fi> wrote:
> 
> Hey Scott,
> 
> In edge links, you can limit multicast and broadcast very severely.
> There is very little point to limit unicast even in edge links, unless
> you want to protect firewall from some owned host sending 1.48M SYN
> pps.

[…]

> Assuming you don't actually run multicast applications and that you
> don't have any esoteric LAN distribution application using broadcast.
> I'd limit edge ports 10pps for mcast and bcast each, and drop excess
> (not put port down or anything). In core ports I'd limit mcast and
> bcast to maybe 2000pps.

If you did have some multicast traffic, like a basic 720p or 1080p video
stream, what’s a good rule of thumb for that?  Assume 5-8 Mb/s.
Just watch a port with an active viewer and go 10-20% above what
you see as a limit for multicast?

Thanks,

Charles

> 
> 
> I find that often when people configure these, they configure the
> limit in bps and slightly below line rate, which is non-sensical.
> 
> On 22 November 2017 at 18:13, Scott Voll <svoll.voip at gmail.com> wrote:
>> So I'm green field with 3850 at the distribution layer and 3650 at the
>> access layer.
>> 
>> Since I don't have anything to start with, what would be save storm control
>> limits to start with on each platform for Broadcast, multicast,and
>> Unicast?
>> 
>> Mgig to the edge, 20gig to the distribution, and 160 gig to the core.
>> 
>> TIA
>> 
>> Scott
>> _______________________________________________
>> 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/
> 
> 
> 
> -- 
>  ++ytti
> _______________________________________________
> 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/