err-disable recovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2013 01:42 AM - edited 03-07-2019 04:23 PM
Dear Experts,
I need an opinion from you that, as you know error detection is enabled by default for all the error types so how safe it is to enable err recovery for all the detectable errors in the network..
will it increase cpu and memory processing????
Regards,
Azeem
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2013 01:58 AM
Azeem,
how safe it is to enable err recovery for all the detectable errors in the network..
It is very dangerous - not because of CPU and memory consumption (those are negligible), but rather because a condition that leads to err-disabling a port is always a cause for concern. Simply reactivating an err-disabled interface automatically may put your network in the precisely same dangerous situation that was actually prevented by err-disabling the interface in the first place.
Therefore, automatic err-disable recovery has to be used very cautiously.
Best regards,
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2013 03:15 AM
Thanks for the reply,
But how can you find out the reason for the port which goes to error disable..
regards,
Azeem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2013 03:33 AM
Hi Azeem,
how can you find out the reason for the port which goes to error disable..
First and foremost, the show int status err-disable command - this command will tell you what ports are err-disabled and what is the reason. In addition, an err-disabling of a port is always logged, so show logging and optionally Syslog etc. can also provide a clue.
Best regards,
Peter
