How to prevent an Interface from shutting down due to excessive errors?
How to prevent an Interface from shutting down due to excessive errors on a CAT 3550. Apparentky there is a error detect cause all and error recovery cause all and some error timer commands. Which are the right sequence of commands to use, so that in spite of excessive errors an interface doesn't shut itself down?
See Log File of my router, I then manually did a no shut on Interface FA0/2/
Jun 20 09:40:35.600: %ETHCNTR-3-HALF_DUX_COLISION_EXCEED_THRESHOLD: Collision at FastEthernet0/2 exceed threshold. Consider as loo
Jun 20 09:40:35.600: %ETHCNTR-3-LOOP_BACK_DETECTED: Loop-back detected on FastEthernet0/2. The port is forced to linkdown.
Jun 20 09:40:37.600: %LINK-5-CHANGED: Interface FastEthernet0/2, changed state to administratively down
Jun 20 09:40:38.600: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2, changed state to down
Jun 23 09:36:01.784: %LINK-3-UPDOWN: Interface FastEthernet0/2, changed state to down
Re: How to prevent an Interface from shutting down due to excess
As far as I know, there is not an option to prevent the switch from disabling itself due to the collisions. You can configure the "errdisable recovery" command to allow the interface to recover from the error-disabled state without having to manually entering shut/no shut. Refer to the following links for more information:
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...