Rate-limit
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-20-2014 10:01 AM
Hi everybody.
I have two Summit x670 (15.4.1.3) switches and I'd like to limit inbound broadcast, multicast and unknown unicast packets on specific ports. So, I've configured rate-limit to 500pps.
config port 3 rate-limit flood broadcast 500
config port 3 rate-limit flood multicast 500
config port 3 rate-limit flood unknown-destmac 500Then I see the output of "show ports 3 stat" command. I see only 10-20 pps, but Flood Rate Exceeded counter is increasing and I have log messages like
Flood Rate Limiting activated on Port 3
I have two Summit x670 (15.4.1.3) switches and I'd like to limit inbound broadcast, multicast and unknown unicast packets on specific ports. So, I've configured rate-limit to 500pps.
config port 3 rate-limit flood broadcast 500
config port 3 rate-limit flood multicast 500
config port 3 rate-limit flood unknown-destmac 500Then I see the output of "show ports 3 stat" command. I see only 10-20 pps, but Flood Rate Exceeded counter is increasing and I have log messages like
Flood Rate Limiting activated on Port 3
23 REPLIES 23
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-23-2016 08:10 AM
yes, this is expected because of the chipsets. Using Meters is a good way to solve that. There're match criteria for all BUM traffic types.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-23-2016 06:08 AM
Hi Stephane,
i have a look at the current Release Notes 21.1.1 - and i found only these:
Configuration of Overhead-bytes in Calculating Rate-Limiting and Rate-Shaping
But this changes nothing regarding the lost or not reliable rate-limit threshold on G2 Switches.
Regards
i have a look at the current Release Notes 21.1.1 - and i found only these:
Configuration of Overhead-bytes in Calculating Rate-Limiting and Rate-Shaping
But this changes nothing regarding the lost or not reliable rate-limit threshold on G2 Switches.
Regards
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-23-2016 06:08 AM
From what I recall, this code has been fixed in 21.1, I had a thread with engineering on that topic. I never tested it, so that would be worth checking in a lab first.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-23-2016 06:08 AM
Hi Stephane,
i do not test because if nothing i written to the release notes engineering do not change the regarding code!
Do you think or know that anything would be changed ?
i do not test because if nothing i written to the release notes engineering do not change the regarding code!
Do you think or know that anything would be changed ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎06-23-2016 06:08 AM
Did you test with 21.1?
