Networking: %SW_MATM-4-MACFLAP_NOTIF: Host is flapping between ports / broadcast storm
A layer-2 loop is making frames circle the network, saturating links and making the whole VLAN crawl.
Host is flapping between portbroadcast stormSpanning tree loop detected Meaning
Someone plugged a switch or cable back into the same network, or spanning tree is off or misconfigured. Find the flapping MAC, unplug the loop, and enable STP protections: BPDU guard on edge ports, root guard, storm control and loop guard.
Common causes
- Cable plugged into two ports of the same network
- Spanning tree disabled or inconsistent
- Unmanaged switch added by a user
- Missing BPDU guard on access ports
- Faulty switch or NIC flooding
⚡ Quick fix
- Find it:
show mac address-table | include <mac> - Unplug the offending cable and enable BPDU guard + storm control
- Verify the root bridge with
show spanning-tree
Detailed fix by platform
Cisco
- text
show spanning-tree summary show interfaces | include broadcasts show logging | include MACFLAP
How to diagnose
- Log — MAC flapping?
- STP — Enabled, correct root?
- Edge ports — BPDU guard?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- arp -a shows (incomplete) Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
- Cannot assign requested address (EADDRNOTAVAIL) Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
- Duplex mismatch: late collisions / CRC errors Networking: Duplex mismatch — late collisions, runts and CRC errors on the switch port
Most viewed in Networking
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
- Idle connections silently dropped by firewall/NAT Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
- DHCPDISCOVER: no free leases Networking: dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via eth0: network 192.168.1.0/24: no free leases
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026