RE: Disabling spanning tree

There's a 99.999% chance this will not be the correct solution due to
another requirement (probably in the 1st or 2nd page of the lab book).

Look at my posts, look at the docs. Not sure what else to tell you guys and
girls.

tv

From: Salah ElShekeil [mailto:salah.elshekeil_at_gmail.com]
Sent: Thursday, April 16, 2009 3:46 PM
To: Jonathan Greenwood II
Cc: loopback 99; Tony Varriale; ccielab
Subject: Re: Disabling spanning tree

the question as it's I didn't change anything

portfast won't disable spanning tree even with bpdufilter !

but still is it right ""no switchport""?!!!! there is no way other than
this?!!

On Thu, Apr 16, 2009 at 11:32 PM, Jonathan Greenwood II <gwood83_at_gmail.com>
wrote:

I'm just curious to see if with it enabled on the interface if the port
still comes up as FWD under the sh spann-tree. If it comes up as Desg/FWD
then I would have to scratch my head, because it still says STP is
operational based upon the port moving into the Forwarding state. Looks
like Ryan just posted the output and it shows STP is still enabled. Any
thoughts??? To be safe I guess I'm still going to go with "no switchport"
Thanks Ryan for the output.

Jonathan Greenwood II
CCIE #22744

On Thu, Apr 16, 2009 at 1:23 PM, loopback 99 <loopback99_at_gmail.com> wrote:

>
>
> I think they are looking for BPDU Filter at the interface level. The Cisco
> documentation says this about it: 'Caution Enabling BPDU filtering on an
> interface is the same as disabling spanning tree on it and can result in
> spanning-tree loops.'
>
> L.
>
>
>

--
Jonathan Greenwood II
CCIE #22744
Blogs and organic groups at http://www.ccie.net <http://www.ccie.net/>