Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
How to recover Cisco Catalyst switches that run Cisco IOS system software from the errDisable port state
If the configuration shows a port to be enabled, but the software on the switch detects an error on the port, the software shuts down that port. In other words, the port is automatically disabled by the switch operating system software because of an error condition encountered on the port.
When a port is error-disabled, it is effectively shut down and no traffic is sent or received on that port. The port LED is set to the color orange, and when the show port command is issued, the port status shows err-disable. If an interface is disabled due to an error condition, the output of the show interface status command displays the interface status as err-disable.
This is an example of how an error-disabled port looks from the Command Line Interface (CLI) of the switch:
Switch#show interfaces gigabitethernet 4/1 status
Port Name Status Vlan Duplex Speed Type Gi4/1 err-disabled 100 full 1000 1000BaseSX
Messages similar to this are sometimes seen if the interface is disabled due to an error condition:
%PM-SP-4-ERR_DISABLE: bpduguard error detected on Gi4/1, putting Gi4/1 in err-disable state
These are the various situations that can cause an interface to go into the err-disable state:
Incorrect configuration of the port channel
Bridge Protocol Data Unit (BPDU) guard violation
UniDirectional Link Detection (UDLD) condition
Port Aggregation Protocol (PAgP) flap
Layer 2 (L2) Tunneling Protocol (L2TP) guard
Dynamic Host Control Protocol (DHCP) snooping rate-limit
To resolve this issue, perform these steps:
Identify and fix the cause of the port error-disabled state (for instance, a problem with cables, Network Interface Cards (NICs), the EtherChannel, and so on).
If the underlying issue is not identified and fixed, the ports just become error-disabled again when the problem reoccurs. Some errors can occur quite often (an example is the error detected by the Bridge Protocol Data Unit (BPDU) portguard, which can occur every two seconds).
After the root cause is determined, troubleshoot and fix the underlying problem. For example, the receipt of a BPDU on a PortFast-enabled access port can cause the port can be in the err-disable state. Verify whether a switch was accidentally connected to that port or whether a hub was connected that created a looping condition.
To troubleshoot other scenarios, refer to the specific feature information in the product documentation.
Reenable the port.
When the source of the problem is fixed, the ports do not automatically become enabled again. Once the source of the problem is fixed, the ports are still disabled (and the port LEDs are still orange); the ports must be reenabled before they become active.
To reenable the interface manually, issue the shutdown and no shutdown interface commands. You can also issue the errdisable recovery cause enable command to set up timeout mechanisms that automatically reenable the port after a configured time period.
Issue the errdisable recovery cause bpduguard and errdisable recovery interval sec commands to reenable the port automatically.
The port may move into errdisable state due to many reasons. For more information on recovering the port from Errdisable state, refer to the followingarticles