cisco:switch:recommended_levels_for_storm_control
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
cisco:switch:recommended_levels_for_storm_control [2022/01/16 19:32] – created aperez | cisco:switch:recommended_levels_for_storm_control [2022/01/16 20:15] (current) – aperez | ||
---|---|---|---|
Line 14: | Line 14: | ||
| | ||
| | ||
- | |||
- | I don't think there are recommended or best practice values. Below is a cut and paste answer from TAC I found in another blog post... | ||
- | + | ||
+ | ---- | ||
+ | |||
+ | |||
+ | I don't think there are recommended or best practice values. Below is a cut and paste answer from TAC I found in another blog post... | ||
"I noticed you want a recommended threshold for the broadcast and multicast storm control. Unfortunately there is no a recommended threshold level because that will depend of the normal broadcast traffic on your network. | "I noticed you want a recommended threshold for the broadcast and multicast storm control. Unfortunately there is no a recommended threshold level because that will depend of the normal broadcast traffic on your network. | ||
Line 25: | Line 27: | ||
1. Clear the counters | 1. Clear the counters | ||
- | - switch# | + | |
2. Leave the switch working during 24 hours | 2. Leave the switch working during 24 hours | ||
- | 3. Port by port (physical interfaces) check the amount of broadcast input | + | 3. Port by port (physical interfaces) check the amount of broadcast input packets, multicast input packets and the total input packets. |
- | packets, multicast | + | Switch#Show interfaces // look for |
+ | | ||
+ | Received broadcasts value (BPI) | ||
+ | (multicast) value (MPI) | ||
- | - Switch#Show interfaces //look for | + | 4. Let's do some mathematics: |
- | - packets | + | To get unicast |
+ | Normal percentage of broadcast = (BPI/TPI) * 100 | ||
+ | Normal percentage of multicast = (MPI/TPI) * 100 | ||
+ | Normal percentage of unicast = (UPI/TPI) * 100 | ||
- | - Received broadcasts value (BPI) | + | That could give you an idea of the daily unicast, multicast and broadcast percentage on your network and could help you to set the proper threshold. |
- | - (multicast) value (MPI) | + | Now the formulas that I am giving you will give a general idea, just to have a projection, nevertheless, |
- | 4. Let's do some mathematics: | + | In order to know the real values, you will require to monitor the traffic during a month or 2 getting the same statistics and perform and statistical analyze based on average and variance to get a closer real-life value. Also probably your network experienced seasons that some times could be on a low |
- | - To get unicast packets you do TPI - BPI, TPI - BPI = UPI | + | traffic season and some times could be on a high traffic season. The traffic analysis is a task that requires getting constant traffic samples to adapt the thresholds to the real life and of course based on the statistical |
- | - Normal percentage of broadcast | + | analysis you will be able to determine the range you need to add to the threshold. For example, let's say you noticed the broadcast |
- | - Normal percentage of multicast = (MPI/TPI) * 100 | + | Please do not think the formula is the best way to determine the threshold, they are just to give a general idea but a deeper research should be done to determine that properly." |
- | - Normal percentage of unicast = (UPI/TPI) * 100 | ||
- | That could give you an idea of the daily unicast, multicast and broadcast percentage on your network and could help you to set the proper threshold. | + | ---- |
- | Now the formulas that I am giving you will give a general idea, just to have a projection, nevertheless the error range is great. | ||
- | In order to know the real values, you will require to monitor the traffic | + | I have seen customer networks working fine with 1 % of broadcast storm control on access ports just to accomodate for ARP request |
- | traffic season and some times could be on a high traffic season. | + | The greater |
- | analysis you will be able to determine | + | About multicast traffic |
+ | |||
+ | |||
+ | |||
+ | Unicast storm-control 60% or more | ||
+ | |||
+ | |||
+ | |||
+ | We have to remember that: | ||
+ | |||
+ | - the feature works on received | ||
+ | |||
+ | - the feature | ||
+ | |||
+ | |||
+ | |||
+ | With low / aggressive thresholds storm control | ||
+ | |||
+ | This happened before introduction of VSS many years ago. | ||
+ | |||
+ | |||
+ | |||
+ | On a L2 uplink trunk port of course thresholds cannot be so low as they carry traffic for multiple VLANs | ||
+ | |||
+ | B 15% | ||
+ | |||
+ | M 30% | ||
+ | |||
+ | U 60% | ||
+ | |||
+ | |||
+ | ---- | ||
- | Please do not think the formula is the best way to determine the threshold, they are just to give a general idea but a deeper research should be done to determine that properly." | ||
cisco/switch/recommended_levels_for_storm_control.1642379542.txt.gz · Last modified: 2022/01/16 19:32 by aperez