07-02-2013 07:08 AM - edited 03-04-2019 08:21 PM
Hello everyone. Can some one help me out in understanding UDLD feature on Cisco switches.tried googling it but could not understand.
Thanks in advance.
Sent from Cisco Technical Support Android App
07-02-2013 08:21 AM
is there something specific about udld you do not understand? you might want to be a bit more explicit in your question otherwise the feedback you will get is links to Cisco reading material.
07-02-2013 03:33 PM
Here's a simple, yet effective, rule-of-thumb about UDLD: DO NOT use UDLD when you are configuring copper ports.
(UDLD works very well on fibre optic ports.)
07-02-2013 04:15 PM
Udld importance while configuring trunks. Udld port aggressive feature
Sent from Cisco Technical Support Android App
07-02-2013 04:23 PM
Udld importance while configuring trunks. Udld port aggressive feature
Sorry, I don't understand you. Is that a statement or is that a question?
07-02-2013 04:30 PM
Its my question...
Sent from Cisco Technical Support Android App
07-02-2013 04:50 PM
Udld importance while configuring trunks. Udld port aggressive feature
802.1Q or ISL trunks have NOTHING to do with UDLD.
07-02-2013 04:56 PM
Hi Leo, which mode
Do you use, normal or aggressive
Sent from Cisco Technical Support iPhone App
07-02-2013 05:44 PM
Do you use, normal or aggressive
Aggressive.
07-02-2013 08:38 PM
Does normal mode make port go into error-disable mode, Leo.
Sent from Cisco Technical Support iPhone App
07-02-2013 11:33 PM
Does normal mode make port go into error-disable mode, Leo.
Both modes can result in error-disable, but the mechanisms are different:
"In normal mode, a protocol determination at the end of the detection process is always based on information received in UDLD messages: whether it's the information about the exchange of proper neighbor identifications or the information about the absence of such proper identifications. Hence, albeit bound by a timer, normal mode determinations are always based on gleaned information, and as such are "event-based". If no such information can be obtained (e.g., because of a bidirectional loss of connectivity), UDLD follows a conservative approach based on the considerations in Section 3 and deems a port to be in "undetermined" state. In other words, normal mode will shut down a port only if it can explicitly determine that the associated link is faulty for an extended period of time."
"In contrast, in aggressive mode, UDLD will also shut down a port if it loses bidirectional connectivity with the neighbor for the same extended period of time mentioned above and subsequently fails repeated last-resort attempts to re-establish communication with the other end of the link. This mode of operation assumes that loss of communication with the neighbor is a meaningful network event in itself and is a symptom of a serious connectivity problem. Because this type of detection can be event-less, and lack of information cannot always be associated to an actual malfunction of the link, this mode is optional and is recommended only in certain scenarios (typically only on point-to-point links where no communication failure between two neighbors is admissible)."
Hope that helps
Rolf
07-03-2013 04:06 PM
Does normal mode make port go into error-disable mode
All modes (aggressive and FAST UDLD) can put the port into error-disable if the hello packets are not being heard.
07-04-2013 07:52 PM
why not normal mode?
I mean is it necessary to use aggressive mode , is aggressive mode useful in real world? Or some disadvantage with aggressive mode.
Sent from Cisco Technical Support iPhone App
07-04-2013 08:07 PM
why not normal mode?
I've never heard of "normal mode" in UDLD.
I mean is it necessary to use aggressive mode , is aggressive mode useful in real world?
I've got 10 Gbps fibre uplinks. I want to make sure that the very first sign that there's an issue of the link, I want all traffic to stop. If I don't turn on UDLD, I would potentially have a network issue if the fibre link goes up/down at regular intervals per minute. If one end does not hear the UDLD hello packet, then it means there could be a potential link issue and the switch will disable the port in question.
07-05-2013 02:04 AM
Hi Leo,
I've never heard of "normal mode" in UDLD.
Check these links:
http://www.cisco.com/en/US/tech/tk389/tk621/technologies_tech_note09186a008009477b.shtml#udldmodes
http://tools.ietf.org/html/rfc5171#section-5.4
It has to be said, though, that the normal mode was always somewhat of a mystery to me. There are conflicting descriptions being circulated about it. The first document I've linked states:
In normal mode, if the link state of the port was determined to be bi-directional and the UDLD information times out, no action is taken by UDLD. The port state for UDLD is marked as undetermined. The port behaves according to its STP state.
However, the RFC 5171 states:
In other words, normal mode will shut down a port only if it can explicitly determine that the associated link is faulty for an extended period of time.
What is the "extended period of time" and how the "explicit determination" is accomplished is not described in any document I have been able to dig out so far.
Best regards,
Peter
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide