error-disable condition

[johnilu]

Can someone explain to me what causes an error-disable condition, and how it is typically corrected.

I have read the Cisco description, but it appears that I am missing something.

 

[BuckWeet]

Usually its from a physical media problem.. do a 'show logging' it should tell you why it went err-disabled.. another possible reason is spanning-tree.. you might have bpduguard enabled.. if the port is in access mode with that feature enabled, if it receives a BPDU, it will shut itself down.



BuckWeet

 

[johnilu]

These are two main conditions. So to correct it you need to correct the problem and the condition is corrected as soon as the reset time is reached?

 

[ADB100]

For an interface to go into the errdisable state one of several conditions need to be met and enabled in the configuration. The output below is from a Catalyst 2950 and shows the verious conditions that would cause a port to errdisable:

cat-2950#sho errdisable detect
ErrDisable Reason Detection status
----------------- ----------------
udld Enabled
bpduguard Enabled
security-violatio Enabled
channel-misconfig Enabled
psecure-violation Enabled
dhcp-rate-limit Enabled
unicast-flood Enabled
vmps Enabled
pagp-flap Enabled
dtp-flap Enabled
link-flap Enabled
gbic-invalid Enabled
loopback Enabled
dhcp-rate-limit Enabled
unicast-flood Enabled
cat-2950#

All the above are enabled by default and the recovery mechanism is by manual intervention. You can however enable automatic recovery with a timer for individual or all conditions:

cat-2950(config)#errdisable recovery interval ?
<30-86400> timer-interval(sec)

HTH

Andy