What i know, UDLD is basically developed for Fiber optics, where chance of
one way communication are more than any thing else. And UDLD uses its own
mechanism to detected unidirectional links.
Where as LoopGuard uses STP mechanism to detect unidirectional links and
mostly enabled for copper links.
HTH
On Sun, Jan 24, 2010 at 3:05 PM, Michael McFarlin <router.genie_at_gmail.com>wrote:
> Experts,
>
> I have a question about UDLD and Loopguard in one of the IERS labs. I don't
> think that loopguard is needed at all here. Why would you have to worry
> about SW1 making the Fa0/15 a designated port if UDLD has already taken the
> port down? By default UDLD acts faster than Loopguard by default right?
>
>
> Task
>
> Administrators of your network are concerned about SW1 and SW2 not
> being able to detect a link failure on port Fa0/15.
>
> Configure SW1 and SW2 so that port Fa0/15 is brought down in the case
> that either switch can send traffic, but not receive, or vice versa.
>
> As an additional precaution, configure SW1 so that interface Fa0/15 is not
> mistakenly elected as a designated port in the above case.
>
> Answer
>
> SW1:
> interface FastEthernet0/15
> udld port aggressive
> spanning-tree guard loop
> SW2:
> interface FastEthernet0/15
> udld port aggressive
>
>
> -Mike
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Sun Jan 24 2010 - 19:49:12 ART
This archive was generated by hypermail 2.2.0 : Thu Feb 04 2010 - 20:28:42 ART