%PM-4-ERR_DISABLE:

[enriquebs]

HI all,

We are having an issue this morning in a switch port, this port connect to a MetroEthernet network managed by our Service Provider, here you can see the log output:

Jul 4 12:28:28: %PM-4-ERR_DISABLE: link-flap error detected on Gi2/0/26, putting Gi2/0/26 in err-disable state (SW01)

Jul 5 08:40:52: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down

Jul 5 08:40:54: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/26, changed state to down

Jul 5 08:40:57: %SYS-5-CONFIG_I: Configured from console by XFCC0003 on vty0 (172.26.26.98)

Jul 5 09:08:53: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down

Jul 5 09:08:59: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/26, changed state to down

Jul 5 09:09:59: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down

Jul 5 09:10:21: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/26, changed state to down

Jul 5 09:11:24: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down

Jul 5 09:11:30: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/26, changed state to down

Jul 5 09:11:47: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down

Jul 5 09:12:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/26, changed state to down

Jul 5 09:13:45: %LINK-5-CHANGED: Interface GigabitEthernet2/0/26, changed state to administratively down

Jul 5 09:13:55: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/26, changed state to down

No way to get the UP state in the port, could be an issue in the MetroEthernet network? any idea?

Thanks a lot in advance,

[leonvd79]

Hello Enrique,

Due to link-flapping your port is error-isabled. Unless you habe configured to recover the port automatically the port stays administratively shut down.

Issue the "show interfaces status err-disabled" command to see the error-disabled ports.

Switch# show interfaces status err-disabled

Port Name Status Reason

Gi2/0/26 err-disabled link-flap

You'll see int Gi2/0/26 listed as disabled due to link-flap.

Verify your configuration if auto recovery is enabled for link-flapping events.

show run | i errdisable

If the line "errdisable recovery link-flap" is missing you can add it to your configuration.

The default time to recover the link is 5 minutes. This can be changed with by adding the "interval N keyword to the errdiable comand where N stands for number of seconds.

HTH

--Leon

* Please rate posts.

[enriquebs]

HI Leon,

At present the interface status is:

GigabitEthernet2/0/26 is down, line protocol is down (notconnect)

We have recovered it typing the no shut command in the interface configuration mode.

As the interface is (notconnect) I think the issue could be in the Service Provider device facing to our switch...

By the way, thanks a lot for the explanation of the autorecovery from a err-disabled port ;)

[ariela · Accepted solution]

Hi,

good doc:

http://www.cisco.com/en/US/tech/tk389/tk621/technologies_tech_note09186a00806cd87b.shtml

Link-flap error

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

Link flap means that the interface continually goes up and down. The interface is put into the errdisabled state if it flaps more than five times in 10 seconds. The common cause of link flap is a Layer 1 issue such as a bad cable, duplex mismatch, or bad Gigabit Interface Converter (GBIC) card. Look at the console messages or the messages that were sent to the syslog server that state the reason for the port shutdown.

%PM-4-ERR_DISABLE: link-flap error detected on Gi4/1, putting Gi4/

1 in err-disable state

Issue this command in order to view the flap values:

cat6knative#show errdisable flap-values

!--- Refer to show errdisable flap-values for more information on the command.

ErrDisable Reason Flaps Time (sec)

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

pagp-flap 3 30

dtp-flap 3 30

link-flap 5 10

Check the cable, and/or the GBIC.

Hope this helps

Regards

Andrea

[enriquebs]

Thanks a lot for the information, it is really useful!!

[rogerio.oliveira121]

I had the same trouble yesterday and the solution for me was apply the command "no udld agressive"

The equipment that I configured was a IE5010 (Industrial Equipment)