ā03-04-2010 11:03 PM - edited ā03-06-2019 10:00 AM
Hi to everyone,
Would be greatful if you guys guide me to get know the best practise while configuring UDLD in service provider environment.
appreciate your help
shiv
Solved! Go to Solution.
ā03-04-2010 11:29 PM
Hi to everyone,
Would be greatful if you guys guide me to get know the best practise while configuring UDLD in service provider environment.
appreciate your help
shiv
Hi Shiv,
Genral recommendation and best practices is that UDLD to be enabled on all ports terminating links where a potential miswiring can take place or on ports where STP is running. UDLD needs to be enabled globally as well as on a per interface basis. The commands to enable UDLD globally and on an interface are as follows:
6K-LV2-CL3(config)# udld enable
6K-LV2-CL3(config)# interface g1/2
6K-LV2-CL3(config-if)# udld port
UDLD supports two modes of operation: normal and aggressive. The recommended mode to use in the vast majority of the network designs is the former, whereas the latter should be used with great care in those cases where a loss of connectivity with a neighbor represents a serious connectivity problem (for example, when a bundled port in an EtherChannel connection loses connectivity with its peer and EtherChannel is not running a protocol such as PAgP or LACP).
While UDLD can be used to detect "directionality" problems on any Ethernet link, another feature should be used in synergy with UDLD to guarantee greater STP robustness: the feature in question is called STP Loopguard.
Loopguard can be enabled either globally or on a per-port basis thus:
6K-LV2-CL3(config)# spanning-tree loopguard default
6K-LV2-CL3(config-if)# spanning-tree guard loop
Hope to Help !!
Ganesh.H
ā03-04-2010 11:29 PM
Hi to everyone,
Would be greatful if you guys guide me to get know the best practise while configuring UDLD in service provider environment.
appreciate your help
shiv
Hi Shiv,
Genral recommendation and best practices is that UDLD to be enabled on all ports terminating links where a potential miswiring can take place or on ports where STP is running. UDLD needs to be enabled globally as well as on a per interface basis. The commands to enable UDLD globally and on an interface are as follows:
6K-LV2-CL3(config)# udld enable
6K-LV2-CL3(config)# interface g1/2
6K-LV2-CL3(config-if)# udld port
UDLD supports two modes of operation: normal and aggressive. The recommended mode to use in the vast majority of the network designs is the former, whereas the latter should be used with great care in those cases where a loss of connectivity with a neighbor represents a serious connectivity problem (for example, when a bundled port in an EtherChannel connection loses connectivity with its peer and EtherChannel is not running a protocol such as PAgP or LACP).
While UDLD can be used to detect "directionality" problems on any Ethernet link, another feature should be used in synergy with UDLD to guarantee greater STP robustness: the feature in question is called STP Loopguard.
Loopguard can be enabled either globally or on a per-port basis thus:
6K-LV2-CL3(config)# spanning-tree loopguard default
6K-LV2-CL3(config-if)# spanning-tree guard loop
Hope to Help !!
Ganesh.H
ā03-04-2010 11:35 PM
hi,
i wanted to configure in aggressive mode since need to track lines terminated to the port closely.Do you have any docs for this pls..
thanks
shiv
ā03-04-2010 11:43 PM
hi,
i wanted to configure in aggressive mode since need to track lines terminated to the port closely.Do you have any docs for this pls..
thanks
shiv
Hi Shiv,
Check out the below link for configuration UDLD in cisco switches
Hope to Help !!
Ganesh.H
ā03-05-2010 12:20 AM
Thank you so much Ganesh
shiv
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