Hands-On Lab: Configuring Storm Control

This hands-on lab configures storm control thresholds on a switch port to limit broadcast and multicast traffic, simulating a broadcast storm and verifying the switch suppresses excess traffic before it can overwhelm the network.

Storm Control ConfigurationBroadcast SuppressionTraffic Threshold Percentage

~3 min read · Updated Sep 23, 2026

Lab Objective

Configure storm control on a switch port with a broadcast traffic threshold, simulate a broadcast storm exceeding that threshold, and verify the switch suppresses the excess traffic rather than forwarding it unchecked.

Lab Purpose

Spanning Tree, covered extensively earlier in this series, prevents the Layer 2 loops that typically cause broadcast storms, but it offers no protection against a single misbehaving device or NIC that floods broadcast traffic without any loop being present at all. Storm control provides a direct traffic-rate safety net independent of loop prevention.

Lab Topology

Switch1 ---- Gi1/0/8 ---- PC-A (traffic source)

Task 1: Configure Broadcast Storm Control

Configure storm control on Gi1/0/8 to limit broadcast traffic to 20% of available bandwidth.

Task 2: Verify Baseline Configuration

Confirm the storm control threshold is correctly applied.

Task 3: Simulate Normal Broadcast Traffic

Generate a modest amount of broadcast traffic (well under the threshold) and confirm it passes through unaffected.

Task 4: Simulate an Excessive Broadcast Storm

Generate broadcast traffic exceeding the configured 20% threshold and verify the switch suppresses the excess.

Task 5: Verify Suppression Statistics

Check the interface counters confirming storm control action was taken.

Solution and Verification

Switch1(config)# interface gigabitethernet1/0/8
Switch1(config-if)# storm-control broadcast level 20.00

Switch1# show storm-control gigabitethernet1/0/8 broadcast

Interface  Filter State   Level   Current
---------  -------------  ------  -------
Gi1/0/8    Forwarding     20.00%  0.00%
-- Confirms the threshold is applied, with
-- current broadcast traffic well below it

-- Modest broadcast traffic generated,
-- staying under 20% of link bandwidth:

Switch1# show storm-control gigabitethernet1/0/8 broadcast

Interface  Filter State   Level   Current
---------  -------------  ------  -------
Gi1/0/8    Forwarding     20.00%  8.20%
-- Still forwarding normally, current
-- level remains below threshold

-- Simulated broadcast storm exceeding 20%
-- generated from PC-A:

Switch1# show storm-control gigabitethernet1/0/8 broadcast

Interface  Filter State   Level   Current
---------  -------------  ------  -------
Gi1/0/8    Blocking       20.00%  34.50%
-- Filter State changed to "Blocking" --
-- the switch is now actively dropping
-- broadcast traffic above the threshold
-- on this port, rather than forwarding
-- everything it receives

Switch1# show interfaces gigabitethernet1/0/8 counters broadcast

Port          Broadcast
Gi1/0/8       184521
-- The broadcast counter confirms
-- significant broadcast volume was seen
-- and partially suppressed by storm control

Key Takeaway

Storm control operates entirely independently of Spanning Tree and loop detection — it protects against excessive broadcast, multicast, or unicast traffic regardless of the cause, whether a genuine Layer 2 loop, a malfunctioning NIC, or a misbehaving application flooding traffic, making it a useful complementary safeguard even on a topology where STP has already eliminated all loops.

Written & researched by Dr. Shahin Siami

Related Articles

Hands-On Lab: Configuring HSRP for IPv6

This hands-on lab configures HSRP for IPv6 between two routers, demonstrating the option to use an automatically generated link-local virtual address rather than manually assigning one, and verifies failover behavior mirrors the IPv4 HSRP lab covered earlier in this series.

Continue

Hands-On Lab: Configuring SVI Autostate Exclude

This hands-on lab configures SVI autostate exclude on a monitoring port within a VLAN, preventing that single inactive port from incorrectly bringing down the SVI for an entire VLAN that still has other active member ports.

Continue

Hands-On Lab: Configuring Private VLANs (PVLANs)

This hands-on lab configures a full Private VLAN structure with a primary VLAN and both isolated and community secondary VLANs, demonstrating fine-grained Layer 2 isolation within a single IP subnet beyond what the simple protected-port feature from an earlier lab can achieve.

Continue

Hands-On Lab: Configuring VLAN Access Control Lists (VACLs)

This hands-on lab configures a VLAN Access Control List using a VLAN access-map to filter traffic within a single VLAN at Layer 2, something a standard router-applied ACL cannot achieve since traffic never leaves the VLAN to reach a routed interface.

Continue

Hands-On Lab: Configuring PVLAN Edge (Protected Ports)

This hands-on lab configures PVLAN Edge (protected ports) on two access ports within the same VLAN, isolating them from each other at Layer 2 while both retain normal connectivity to an uplink port, demonstrating a lightweight isolation feature that requires no separate VLAN.

Continue

Hands-On Lab: Configuring Flex Links

This hands-on lab configures Flex Links between two uplinks on an access switch, providing sub-second failover without relying on Spanning Tree at all, and verifies traffic automatically shifts to the backup link when the primary fails.

Continue