From: Senthil Kumar (senthil.kumar@intechnology.co.uk)
Date: Wed Nov 06 2002 - 07:29:58 GMT-3
this is exactly what it is.. enable loopguard on a root port, which never
lets it originate bpdu's..
and enable root guard on access ports, where a bpdu should never be
received.
-----Original Message-----
From: Donny MATEO [mailto:donny.mateo@sg.ca-indosuez.com]
Sent: 06 November 2002 10:02
To: Szeto Jeff
Cc: ccielab@groupstudy.com; nobody@groupstudy.com
Subject: Re: 3550 root guard and loop guard
Root guard, is used to make sure the port will never become a root port. It
works in such as way
that if the spanning tree calculation result on the port with the root guard
configured selected as
the rootport (meaning a bpdu is received on this interface with higher
bridge ID), the port is put
in incosistent state (read as blocked), and the spanning tree will select
another port as the root
port.
For loopguard, what it do is to make sure that your Root port and alternate
will never become a
Designated port for "other" switch.
So in other words, your switch will never be the switch in the root path for
others. Imagine if
you're on access switch and suddenly the uplink of the access switch became
the Designated port of
the distribution switch, something must be wrong. Use loopguard to prevent
this from happening.
That is my understanding, perhaps other can give more.
Donny
"Szeto Jeff"
<jytszeto@hotmail To:
ccielab@groupstudy.com
.com> cc:
Sent by: Subject: 3550 root guard and
loop guard
nobody@groupstudy
.com
06-11-2002 16:45
Please respond to
"Szeto Jeff"
Hi Group,
I am reading the config guide and do not clear about the root and loop
guard.
Why root guard prevent the remote switch that connecting to the local switch
from becoming the root?
The following, about the loop guard, is copied from the guide:
"You can use loop guard to prevent alternate or root ports from becoming
designated ports because of a failure that leads to a unidirectional link"
Actually, what the loop guard do?
Thank you in advance.
Jeff
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:53 GMT-3