Solved: PM-4-ERR_DISABLE-udld-err-disable

Shibu1978 · ‎05-10-2011

Dear All,

Today one of the interface where the STM-1 link connected in cisco 3750 Switch went to err-disable state . later i had to shut & no shut the port to bring up the port to operational state. what could be the issue? following are the details.

May 10 2011 14:31:22.161 UAE: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi1/0/25, transmit/receive loop detected

May 10 2011 14:31:22.161 UAE: %PM-4-ERR_DISABLE: udld error detected on Gi1/0/25, putting Gi1/0/25 in err-disable state

May 10 2011 14:31:23.167 UAE: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/25, changed state to down

Connection

========

Port g1/0/25 ------------------------------- 1000BaseSX SFP------------Multimode fiber --------------------1000BaseSX SFP-------Multiplexer(Alcatel)

=========================================

udld aggressive is globaly enabled and to port as well.

STM-STACK-1#sh udld g1/0/25

Interface Gi1/0/25

Port enable administrative configuration setting: Follows device default

Port enable operational state: Enabled / in aggressive mode

Current bidirectional state: Unknown

Current operational state: Advertisement

Message interval: 7

Time out interval: 5

No neighbor cache information stored

====================================

==============================================================

STM-STACK-1#sh ver

Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 12.2(52)SE, RELEASE SOFTWARE (fc3)

Compiled Fri 25-Sep-09 07:33 by sasyamal

Image text-base: 0x00003000, data-base: 0x02400000

ROM: Bootstrap program is C3750E boot loader

BOOTLDR: C3750E Boot Loader (C3750E-HBOOT-M) Version 12.2(44r)SE3, RELEASE SOFTWARE (fc3)

STM-STACK-1 uptime is 48 weeks, 5 days, 12 hours, 43 minutes

System returned to ROM by power-on

System restarted at 03:04:30 Thu Jun 3 2010

System image file is "flash:c3750e-universalk9-mz.122-52.SE.bin"

Thanks

Antonio Knox · ‎05-10-2011

If this is a recurring issue, you may want to keep a keen eye on this. There is a reason for UDLD to detect a link failure, and you should know what it is so that it can be fixed. Make sure the connectors are securely fastened and double check configs on the fiber port.

If this was a 'hiccup' situation and there is a logical reason for the failure (which you have found and fixed), there's no reason to be concerned, UDLD is just doing it's job. Note: issuing a 'shut/no shut' is a band-aid solution. You want to solve the issue permanently.

View solution in original post

Antonio Knox · ‎05-10-2011

You are running UDLD aggressive mode. It basically polls a fiber link for connectivity in both directions, and when your switch detects uni-directional traffic on a fiber link, it will shut the port down (err-disable) to avoid a loop developing. I'd check the fiber or the fiber modules on both ends to make sure there's no issues. Here's more info on the UDLD feature:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3550/software/release/12.1_19_ea1/configuration/guide/swudld.html

Hope that helps.

Latchum Naidu · ‎05-10-2011

Hi Shibu,

This because that the UDLD Protocol disabled an interface because it detected connections between neighbors that were functioning only in one direction, which might potentially cause spanning-tree loops or interfere with connectivity. The cause is likely to be hardware related, either due to a bad port, a bad cable, or a misconfigured cable.

Please try to correct the configuration or locate the bad cable. If you are not successful, copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support user EXEC command to gather data that might provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.

Please click on the correct answer on all posts if they answered your question.
Regards,
Naidu.

Shibu1978 · ‎05-10-2011

Hi both,

As i checked i could not see any fault on the fiber or the port. So i just did shut & no shut . interface came back to normal.

after that I am not seeing any errors or issues for the last 2.30 hours . should i leave it or stil have to worry ?

Thanks

Antonio Knox · ‎05-10-2011

If this is a recurring issue, you may want to keep a keen eye on this. There is a reason for UDLD to detect a link failure, and you should know what it is so that it can be fixed. Make sure the connectors are securely fastened and double check configs on the fiber port.

If this was a 'hiccup' situation and there is a logical reason for the failure (which you have found and fixed), there's no reason to be concerned, UDLD is just doing it's job. Note: issuing a 'shut/no shut' is a band-aid solution. You want to solve the issue permanently.

Shibu1978 · ‎05-10-2011

Thanks.

will keep an eye on the device.