Difference between revisions of "Errdisable Cisco IOS"
From Teknologisk videncenter
m (New page: To use Cisco IOS error disable feature you need to make sure what features are possible on the platform. <source lang=cli> PB1#show version <notice>Output omitted.........</notice> System ...) |
m (→BPDU guard) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 36: | Line 36: | ||
Interfaces that will be enabled at the next timeout: | Interfaces that will be enabled at the next timeout: | ||
</source> | </source> | ||
| − | =BPDU guard= | + | =BPDU guard error recovery= |
| + | If BPDU guard are enabled on a interface and the port receives a BPDU the port will go to errdisabled state, and need to manually be recovered by a '''shutdown''' and a '''no shutdown''' to enter normal port operation. With error recovery the port will recover itself. In the example below fa0/1 - 12 will recover in 120 seconds after receiving a BPDU. | ||
<source lang=cli> | <source lang=cli> | ||
PB1(config)#<input>errdisable recovery cause bpduguard</input> | PB1(config)#<input>errdisable recovery cause bpduguard</input> | ||
PB1(config)#<input>errdisable recovery interval 120</input> | PB1(config)#<input>errdisable recovery interval 120</input> | ||
PB1(config)#<input>int ran fa0/1 - 12</input> | PB1(config)#<input>int ran fa0/1 - 12</input> | ||
| − | PB1(config-if-range)#spanning-tree bpduguard enable | + | PB1(config-if-range)#<input>spanning-tree bpduguard enable</input> |
PB1(config)#<input><CTRL-Z></input> | PB1(config)#<input><CTRL-Z></input> | ||
| − | PB1#show errdisable recovery | + | PB1#<input>show errdisable recovery</input> |
ErrDisable Reason Timer Status | ErrDisable Reason Timer Status | ||
----------------- -------------- | ----------------- -------------- | ||
Latest revision as of 14:24, 21 March 2010
To use Cisco IOS error disable feature you need to make sure what features are possible on the platform.
PB1#show version
<notice>Output omitted.........</notice>
System image file is "flash:/c3550-ipservicesk9-mz.122-44.SE6.bin"
<notice>Output omitted.........</notice>
Model number: WS-C3550-24-EMI
<notice>Output omitted.........</notice>
PB1#<input>show errdisable recovery</input>
ErrDisable Reason Timer Status
----------------- --------------
arp-inspection Disabled
bpduguard Disabled
channel-misconfig Disabled
dhcp-rate-limit Disabled
dtp-flap Disabled
gbic-invalid Disabled
l2ptguard Disabled
link-flap Disabled
mac-limit Disabled
link-monitor-failure Disabled
loopback Disabled
oam-remote-failure Disabled
pagp-flap Disabled
port-mode-failure Disabled
psecure-violation Disabled
security-violation Disabled
sfp-config-mismatch Disabled
storm-control Disabled
udld Disabled
unicast-flood Disabled
vmps Disabled
Timer interval: 300 seconds
Interfaces that will be enabled at the next timeout:BPDU guard error recovery
If BPDU guard are enabled on a interface and the port receives a BPDU the port will go to errdisabled state, and need to manually be recovered by a shutdown and a no shutdown to enter normal port operation. With error recovery the port will recover itself. In the example below fa0/1 - 12 will recover in 120 seconds after receiving a BPDU.
PB1(config)#<input>errdisable recovery cause bpduguard</input>
PB1(config)#<input>errdisable recovery interval 120</input>
PB1(config)#<input>int ran fa0/1 - 12</input>
PB1(config-if-range)#<input>spanning-tree bpduguard enable</input>
PB1(config)#<input><CTRL-Z></input>
PB1#<input>show errdisable recovery</input>
ErrDisable Reason Timer Status
----------------- --------------
arp-inspection Disabled
bpduguard Enabled
channel-misconfig Disabled
<notice>Output omitted.........</notice>
Timer interval: 120 seconds
Interfaces that will be enabled at the next timeout: