What causes a port to be placed in the err-disabled state?

Issuing the shutdown command on a port manually administratively disables it, putting it into an 'administratively down' state, not 'err-disabled'.

A port security violation occurs when a configured security policy, such as exceeding the maximum allowed MAC addresses on a port or detecting a MAC address spoof, is breached. When this happens, the switch places the port into an err-disabled state to protect the network from unauthorized access or malicious activity.

If nothing is plugged into a port, it will typically be in a 'notconnect' or 'down' state (physical layer issue), but not 'err-disabled'.

High latency indicates network congestion or delay but does not directly trigger the err-disabled state on a switch port; it affects performance, not port operational status in this manner.