The ErrDisable feature is implemented to handle special situations where the switch detected excessive or late collisions on a port, port duplex misconfiguration, EtherChannel misconfiguration, Bridge Protocol Data Unit (BPDU) port-guard violation, UniDirectional Link Detection (UDLD), and other (miscellaneous) causes.
The error-disable function allows the switch to shut down a port when it encounters physical, driver or configuration problems. A port being error-disabled is not by itself a cause for alarm, but a symptom of a problem that must be resolved.
Troubleshooting an ErrDisable Port on the CatOS Platforms:
Determine cause of ErrDisable error on the port. For example, a show port might indicate a parameter mismatch of EtherChannel.
In this case, it was err-disable due to channel-misconfig.
Fix identified ErrDisable cause (for example, match parameters on either end of link).
After fixing cause of problem , the port will still be disabled (and the port LEDs are still orange). Re enable the port manually by entering set port enable.
Troubleshooting an ErrDisable Port on the IOS Platforms:
When a port is in error-disabled state, it is effectively shut down and no traffic is sent or received on that port. The port LED is set to the orange color and, when you issue the show interfaces command, the port status shows as Errdisabled.
Following is an example of what an error-disabled port looks like:
switch#show int G1/0/1GigabitEthernet1/0/1 is down, line protocol is down (err-disabled)
To find out the main reason for err-disable state. In our case it is port security violation on port Gi1/0/1.
switch#show interfaces status err-disabledPort Name Status ReasonGi1/0/1 SERVER01 err-disabled psecure-violationGi1/0/46 err-disabled psecure-violationGi2/0/12 err-disabled psecure-violation
To recover a port that is in an Errdisable state, manual intervention is required, and the administrator must access the switch and configure the specific port with 'shutdown' followed by the 'no shutdown' command. This command sequence will enable the port again, however, if the problem persists expect to find the port in Errdisable state again soon.
you may not want a port with a security violation to come back up without administrative intervention, but a port downed due to a flapping host you might want automatically turned back on after a few minutes. You can issue the "errdisable recovery cause" command to configure and see a list of switch port errors that the switch can automatically recovery from.
In the below example setting Errdisable autorecovery for BPDU GUARD.
The second option you can configure is the time interval in which the switch waits before it re-enables the err-disabled port. The default recovery interval is 300 seconds.
While this err-disable recovery feature can be a great time saver it is still important to investigate and correct the real issue that is causing the switch ports to fail into an err-disabled state.
Hi TeamEverytime when I try to downlaod firmware for a switch it doesnt allow me to do it, though I signed in with my credentials whenever I select the firmware I choose to download it comes up with an error and not allowing me to download. (tried in diff...
Hi, I want to plug links from two different internet providers into our Cisco1001x router and have it load balance between them to send the traffic out the fastest link at any time, however I don't get anything when I google this. Or, I want to buy a Cisc...
Hello dear friends
We have Cisco switch 9200L-48 port which the ports from 1-36 working normally,but from 37-48 only ports number 38 and 40 are working.
when you get status about the ports from CLI it shows that the ports 41-48 are up and connected to dev...
I am having a issue when linking two routers together. 9k and 1k is using a GLC-SX-MMD SFP’s and connected via a OM4 MMF fiber cable. Both routers seem to be compatible with the sfps, however when connecting the two routers the 9k goes in a UP/UP state ho...