Re: Spanning Tree Root Guard Vs Loop Guard

From: Joe Astorino <joeastorino1982_at_gmail.com>
Date: Thu, 1 Sep 2011 12:09:31 -0400

A few things to keep in mind:

1) These are completely different features. Loopguard is used to prevent
bridging loops usually as a result of unidirectional links. Rootguard
ensures that unauthorized switches don't take over as your root bridge

2) They are not compatible because you configure loopguard on non-designated
ports and you configure rootguard on designated ports

On Thu, Sep 1, 2011 at 11:24 AM, dia.aliou_at_gmail.com <dia.aliou_at_gmail.com>wrote:

> Hi Clark,
>
> In my understanding there is no difference enabling Loop Guard globally or
> under the port.
> I have not tested it, but bused on Doccd, you cannot enable loop guard and
> root guard at the same time.
>
> HTH,
>
> Aliou
>
> On Thursday, 1 September 2011, Clark, Neil wrote:
>
> > Hi Guys,
> >
> > I have got a quick question regarding Root guard vs loop guard.
> >
> > If you enable loop guard globally does it have any other affect other
> > than to enable Loop guard on every port?
> >
> > And if you have Root guard configured on ports and you enable Loop guard
> > Globally does this have any adverse affects??
> >
> > Any thoughts which is the a better route to go and why??
> >
> > Thanks
> >
> > Neil
> >
> >
> >
> >
> >
> > _______________________________________________________
> > Atos and Atos Consulting are trading names used by the Atos group. The
> > following trading entities are registered in England and Wales: Atos IT
> > Services UK Limited (registered number 01245534), Atos Consulting Limited
> > (registered number 04312380) and Atos IT Solutions and Services Limited
> > (registered number 01203466) The registered office for each is at 4
> Triton
> > Square, Regents Place, London, NW1 3HG. The VAT No. for each is:
> > GB232327983
> >
> > This e-mail and the documents attached are confidential and intended
> solely
> > for the addressee, and may contain confidential or privileged
> information.
> > If
> > you receive this e-mail in error, you are not authorised to copy,
> disclose,
> > use or retain it. Please notify the sender immediately and delete this
> > email
> > from your systems. As emails may be intercepted, amended or lost, they
> > are
> > not secure. Atos therefore can accept no liability for any errors or
> their
> > content. Although Atos endeavours to maintain a virus-free network, we
> do
> > not
> > warrant that this transmission is virus-free and can accept no liability
> > for
> > any damages resulting from any virus transmitted. The risks are deemed to
> > be
> > accepted by everyone who communicates with Atos by email.
> > _______________________________________________________
> >
> >
> > 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Regards,
Joe Astorino
CCIE #24347
Blog: http://astorinonetworks.com
"He not busy being born is busy dying" - Dylan
Blogs and organic groups at http://www.ccie.net
Received on Thu Sep 01 2011 - 12:09:31 ART

This archive was generated by hypermail 2.2.0 : Sat Oct 01 2011 - 07:26:25 ART