Recently I managed to trigger storm control the university end-point I was using (they told me it triggers at 10% bandwidth broadcast traffic). The end-point had a switch plugged in, the switch had a PC and DHCP router plugged in (both switch and router are home category). I'm not sure what happened, by I may have accidentally plugged a port of the switch into another port of the switch (all my cables were blue …), creating a loop for a few minutes, while I was moving everything around. Could this generate a broadcast storm? It might be important: the PC runs nmap and arp-scan every 15 minutes on our local network.
Broadcast Storm Generation Explained
broadcast
Related Topic
- HP ProCurve WOL – Auto WOL MAC Address of Offline Devices
- Cisco Broadcast and Multicast Storm Control on Distribution Switches
- Switch – Recommended Cisco storm-control broadcast and multicast threshold value for user PC
- Switch – WDS and how can it cause a broadcast storm
- Broadcast Storm – Can a Broadcast Storm Cause Physical Damage to Hardware?
- Broadcast Traffic – Do Routers Forward Broadcast Traffic?
Best Answer
A bridge loop is practically guaranteed to cause a broadcast storm. A broadcast frame entering any switch port will get forwarded to both looped ports, both copies consequently returning back to the switch, both being forwarded out the original source port and also sent into the loop again, circling until you break the loop.
Essentially, for each broadcast frame entering the switch, you get two frames exiting the switch again on each port per forwarding cycle. With a switching latency of 20 μs, that's 100,000 frames/s.
For a simple ARP request, each frame runs 528 bits over the wire, so 100K frames/s are already more than 50 Mbit/s.
Now, a second broadcast frame comes along and enters the switch, producing another 100,000 frames/s...