A Cisco access port goes down just after a device is connected. Before resetting it, confirm whether the switch placed it in an err-disabled state because the port received a BPDU.
show interfaces status err-disabled
show logging | include BPDU|ERR_DISABLE
show running-config interface GigabitEthernet1/0/24
show errdisable recovery
Compare the timestamp and interface in the log. An err-disabled port can have several causes, so use the reason reported by the switch. Check the physical connection, patch-panel records, and what changed at that time. A downstream switch connected to an endpoint port is one explanation. An uplink accidentally configured with endpoint protections is another.
Worked example. A user moves a desktop cable to a small switch. The Catalyst records a BPDU Guard event on the wall-port uplink. The engineer traces the cable, removes the downstream switch, and restores the approved endpoint connection. Recover the affected port using the established change procedure after correcting the cause. Verify the port stays up, no new guard event appears, and the endpoint lands in its expected VLAN.
Cisco documents the relationship between BPDU Guard and err-disable recovery. See Cisco’s err-disable recovery guide and our Catalyst STP troubleshooting guide.