Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
The switch shut the port down because a security or protection feature detected a violation.
%PM-4-ERR_DISABLE: psecure-violation error detectedputting Gi0/5 in err-disable statePort is in err-disabled state Meaning
Read the cause (show errdisable recovery), fix it (extra MAC addresses with port security, BPDU guard, loop or link-flap), then recover with shutdown / no shutdown or enable errdisable recovery cause ... interval 300.
Common causes
- Port security saw more MAC addresses than allowed
- BPDU guard triggered by a switch on an edge port
- Link flap or loopback detected
- Unsupported SFP inserted
- UDLD or DHCP-snooping rate violation
⚡ Quick fix
- Show the cause:
show interfaces status err-disabled - Fix it, then
shutdownandno shutdownthe port - Enable errdisable auto-recovery with a sensible interval
Detailed fix by platform
Cisco
- text
show interfaces status err-disabled configure terminal interface Gi0/5 shutdown no shutdown
How to diagnose
- Cause — Which feature?
- Offending device — Removed?
- Recovery — Manual or timed?
🔧 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
- 4-way handshake timeout / Incorrect password Networking: wlan0: WPA: 4-way handshake failed - pre-shared key may be incorrect / WRONG_KEY
- 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
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