errdisable recovery
errdisable recovery cause
{
all
|
cause
}
no errdisable recovery cause
{
all
|
cause
}
errdisable recovery interval
time
no errdisable recovery interval
time
The ports in the error-disabled state are not recovered.
- all
- Enables the ports torecover automatically from an error-disabled state caused by reasons such as BPDU guard violation, the number of inError packets exceeding the configured threshold, a loop detection violation, or the reception of a critical event from the remote device in the case of an EFM-OAM interface.
- causecause
- Configures the ports to recover from an error-disabled state caused by one of the following reasons:
- bpduguard
- Configures the port to recover from the error-disabled state if the state was caused because of BPDU guard violation.
- lag-operspeed-mismatch
- Configures the port to recover from the error-disabled state if the state was caused because of lag operational speed mismatch.
- loam-critical-event
- Configures the EFM-OAM interface to recover from the error-disabled state if the state was caused due to reception of a critical event from the remote device.
- loop-detection
- Configures the port to recover from the error-disabled state if the state was caused because of loop detection.
- packet-inerror-detect
- Configures the port to recover from the error-disabled state if the state was caused because the number of inError packets exceeded the configured threshold.
- pvstplus-protect
- Configures the port to recover from the error-disabled state if the state was caused because the PVST+ Protect feature is enabled.
- interval
- Configures a timeout value for the recovery mechanism when the port is in an error-disabled state. Upon the expiry of the timeout value, the ports are automatically recovered.
Global configuration mode
When automatic recovery re-enables the port, the port is not in the error-disabled state, but it can remain down for other reasons, such as the Tx/Rx of the fibre optic not being seated properly. Thus, the port is not able to receive the signal from the other side. In this case, after the optic is inserted correctly, you must manually disable the port and then re-enable it.
The
no form of the
errdisable recovery cause command disables the error-disabled recover functionality.
The
no form of the
errdisable recovery interval command reverts to the default recovery time interval value.
The following example configures the device to recover the port from the error-disabled state caused because of BPDU guard violation.
device(config)# errdisable recovery cause bpduguard
The following example configures the device to recover the EFM-OAM interface from the error-disabled state caused by reception of a critical event from the remote device.
device(config)# errdisable recovery cause loam-critical-event
The following example configures the device to recover the port from the error-disabled state caused because of loop detection.
device(config)# errdisable recovery cause loop-detection
The following example configures the device to recover the port from the error-disabled state caused because the number of inError packets exceeded the configured threshold.
device(config)# errdisable recovery cause packet-inerror-detect
The following example configures the device to recover the port from the error-disabled state caused because PVST+ Protect was enabled.
device(config)# errdisable recovery cause pvstplus-protect
The following example configures the device to recover the port from the error-disabled state caused because lag operation speed mismatch enabled.
device(config)# errdisable recovery cause lag-operspeed-mismatch
| Release version | Command history |
|---|---|
| 08.0.30 | The loam-critical-event option was introduced. |
| 08.0.30mb | The pvstplus-protect option was introduced. |
| 08.0.90 | The lag-operspeed-mismatch option was introduced. |