Errdisable Port State Recovery

[daywalker28]

All,

I am testing 2960 24 S  with storm-control  and Errdisable Port timer interval 60s , connected HUB on fa0/17 to make traffic / loop

After Strom Control detection the interface goes down thats ok  after 60s they will try to recover the interface and going up although the loop is still there.

For my understanding if the interface detect still a loop on that interface they will disable the port again for 60s and will check  again

any idea ?

00:55:10: %PM-4-ERR_DISABLE: storm-control error detected on Fa0/17, putting Fa0/17 in err-disable state

00:55:10: %STORM_CONTROL-3-SHUTDOWN: A packet storm was detected on Fa0/17. The interface has been disabled.

00:55:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down

00:55:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to down

00:55:12: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to down

00:56:10: %PM-4-ERR_RECOVER: Attempting to recover from storm-control err-disable state on Fa0/17

00:56:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up

00:56:13: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to up

00:56:14: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to up

OB#sh errdisable recovery

ErrDisable Reason            Timer Status

-----------------            --------------

bpduguard                    Disabled

channel-misconfig (STP)      Disabled

dhcp-rate-limit              Disabled

dtp-flap                     Disabled

gbic-invalid                 Disabled

inline-power                 Disabled

link-flap                    Disabled

mac-limit                    Disabled

loopback                     Disabled

pagp-flap                    Disabled

port-mode-failure            Disabled

pppoe-ia-rate-limit          Disabled

psecure-violation            Disabled

security-violation           Disabled

sfp-config-mismatch          Disabled

small-frame                  Disabled

storm-control                Enabled

udld                         Disabled

vmps                         Disabled

psp                          Disabled

Timer interval: 60 seconds

interface FastEthernet0/17

storm-control broadcast level 15.00

storm-control action shutdown

storm-control action trap

spanning-tree portfast

spanning-tree bpdufilter enable

Thanks

[cadet alain]

Hi,

storm control has got nothing to do with loops, it's just a feature that measures the amount of broadcast or unicast or multicast frames entering the port and when a threshold is attained it will either drop the traffic or errdisable the port which is your case.

when you reenable the port if the level of broadcast is below the threshold then the port will stay up.

Regards.

Alain

[daywalker28]

Hi Alain,

thanks for your reply. As you descripted with reenable the port .. but I did not reenabled the port manually.. they should check if  still Broadcast ,unicast  etc. reached the threshold if yes the interface should go down again at second time but during the second time check the port is up automaticly.

Regards,

Ahmet

[cadet alain]

Hi,

So that probably means the level of broadcast is then under the configured threshold, can you do sh storm-control broadcast as well as sh interface to verify.

Regards.

Alain

[daywalker28]

Hi,

here the output

before

OB#sh storm-control broadcast

Interface  Filter State   Upper        Lower        Current

---------  -------------  -----------  -----------  ----------

Fa0/15     Link Down         1.00%        1.00%        0.00%

Fa0/16     Link Down         1.00%        1.00%        0.00%

Fa0/17     Forwarding       15.00%       15.00%        0.00%

Fa0/18     Link Down         1.00%        1.00%        0.00%

Fa0/19     Link Down         1.00%        1.00%        0.00%

Fa0/20     Link Down         1.00%        1.00%        0.00%

OB#sh int fa0/17

FastEthernet0/17 is up, line protocol is up (connected)

  Hardware is Fast Ethernet, address is 0023.3437.3111 (bia 0023.3437.3111)

  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 100Mb/s, media type is 10/100BaseTX

  input flow-control is off, output flow-control is unsupported

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 17:47:48, output 00:00:06, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 260000 bits/sec, 374 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     4281334 packets input, 685056789 bytes, 0 no buffer

     Received 4280209 broadcasts (3899080 multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 3899080 multicast, 0 pause input

     0 input packets with dribble condition detected

     11862 packets output, 1276994 bytes, 0 underruns

     0 output errors, 0 collisions, 2 interface resets

     0 unknown protocol drops

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier, 0 pause output

     0 output buffer failures, 0 output buffers swapped out

after

OB#sh storm-control broadcast

Interface  Filter State   Upper        Lower        Current

---------  -------------  -----------  -----------  ----------

Fa0/15     Link Down         1.00%        1.00%        0.00%

Fa0/16     Link Down         1.00%        1.00%        0.00%

Fa0/17     Forwarding       15.00%       15.00%        0.00%

Fa0/18     Link Down         1.00%        1.00%        0.00%

Fa0/19     Link Down         1.00%        1.00%        0.00%

Fa0/20     Link Down         1.00%        1.00%        0.00%

OB#sh int fa0/17

FastEthernet0/17 is up, line protocol is up (connected)

  Hardware is Fast Ethernet, address is 0023.3437.3111 (bia 0023.3437.3111)

  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 2/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 100Mb/s, media type is 10/100BaseTX

  input flow-control is off, output flow-control is unsupported

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 17:52:50, output 00:00:21, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 878000 bits/sec, 793 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     4643316 packets input, 738767326 bytes, 0 no buffer

     Received 4641947 broadcasts (4231292 multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 4231292 multicast, 0 pause input

     0 input packets with dribble condition detected

     11992 packets output, 1291254 bytes, 0 underruns

     0 output errors, 0 collisions, 2 interface resets

     0 unknown protocol drops

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier, 0 pause output

     0 output buffer failures, 0 output buffers swapped out

Regards,

Ahmet

[cadet alain]

Hi,

storm-control was not in effect in both cases as the current broadcast level was under the threshold.

Regards.

Alain

[amikat]

Hi,

For how long does your fa0/17 interface go up after re-enabled via the timer? As the traffic measurements and comparisons are based on 1 second time interval it should always go up for at least 1 second after re-enabled even if the loop remains there.

Best regards,

Antonin

[daywalker28]

Hi,

the Fa0/17 goes up after the timer and was still up I don't see any logs.

Best Regards,

Ahmet