Home
LAN
LAN General
What is UDLD protocol ?
LAN
LAN General
What is UDLD protocol ? Google Translation
Main Menu
| Home |
| Useful Links |
| Public Route Server |
| Download |
Advertisements
Who's Online
Latest Articles
- Cisco AUX port for back door emergency link configuration
- Multilink PPP protocol configuration
- Cisco HDLC WAN protocol
- How to install sslexplorer on SuSE linux
- How to convert Cisco AP521 back into stand alone mode
- [log] :Problem with RX packet, length is 1, what is it?
- sslexplorer invalid credentials on SuSE / Linux
- Default password for Cisco AP 521
Popular
- Enable Telnet on IE7.0 with Windows XP and Vista
- How to create loopback interface on Windows XP
- Cisco 7200 Simulator - Dynamips installation for window
- BGP sample configuration guide - Cisco
- How IP-helper address works?
- BGP sample configuration Case 1-1
- BGP Community String for Verizon Business AS701
- Network Settings In VMWare Player
| What is UDLD protocol ? |
|
|
|
| Written by CiscoNET | ||
In order to detect the unidirectional links before the forwarding loop is created, Cisco designed and implemented the UDLD protocol. UDLD is a Layer 2 (L2) protocol that works with the Layer 1 (L1) mechanisms to determine the physical status of a link. At L1, auto-negotiation takes care of physical signaling and fault detection. UDLD performs tasks that auto-negotiation cannot perform, such as detecting the identities of neighbors and shutting down misconnected ports. When you enable both auto-negotiation and UDLD, L1 and L2 detections work together to prevent physical and logical unidirectional connections and the malfunctioning of other protocols. UDLD works by exchanging protocol packets between the neighboring devices. In order for UDLD to work, both devices on the link must support UDLD and have it enabled on respective ports. Each switch port configured for UDLD will send UDLD protocol packets containing the port's own device/port ID, and the neighbor's device/port IDs seen by UDLD on that port. Neighboring ports should see their own device/port ID (echo) in the packets received from the other side. If the port does not see its own device/port ID in the incoming UDLD packets for a specific duration of time, the link is considered unidirectional.
Reference:
http://www.cisco.com/warp/public/473/77.html |
||
| < Prev |
|---|























