This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
A broadcast storm is a loop or a faulty host filling a VLAN. Storm control drops or shuts a port when the rate passes a threshold. The calculator turns a percent or a packet rate into a number. It does not configure a switch. The first action is still to find the loop, not to raise the threshold until the storm fits.
One port or one VLAN you administer. Write the threshold and what the switch will do. Do not mirror the storm onto a laptop you did not plan, and do not disable storm control as a test.
A spanning-tree fix, if that is the cause, is the switching page. This hour records the threshold.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name the switch and the VLAN.
- Write the symptom.
- Pick a threshold you can explain.
- Do not raise it to hide the storm.
- Do not disable the control.
- Stop before a second change.
Mistakes that outlive the command
Broadcast Storms and Storm Control goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Disabling storm control to watch.
- A threshold of 100 percent.
- A capture of a VLAN you were not asked to take.
- Changing STP and storm control together.
- A switch you do not administer.
Decisions to write down
One decision for Broadcast Storms and Storm Control: The switch is yours. The threshold is below a flood. The control stays on. No extra capture. And one change is planned or none yet.
Checks before you call it done
Confirm this before you call the change done: The VLAN is written. The threshold is written. The action is drop or shutdown. The control was not disabled. And no second feature was started. If one of those fails, stop.
Before you leave the device
Broadcast Storms and Storm Control ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.