From: Ali AlKaff (asalkaff@msn.com)
Date: Sat Apr 08 2006 - 15:13:53 GMT-3
I think you're right. I can see that, too. So that then confirms that both
features are mutually exclusive regardless of whether they're applied
globally in conjunction with PortFast or individually on the interface.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Bob
Sinclair
Sent: Saturday, 08 April 2006 21:10
To: Ali AlKaff; 'Cisco certification'
Subject: Re: BPDU Guard & BPDU Filter Mutually Exclusive?
Ali,
This combination of commands:
spanning-tree portfast default
spanning-tree portfast bpdufilter default
will cause all ports to be configured for portfast, and to automatically
disable portfast if a bpdu is received on that port.
This command on an interface:
interface FastEthernet0/1
spanning-tree bpdugaurd enable
will error-disable a port if it receives a bpdu and is configured for
portfast.
So, I do not see how the global filter and the interface guard can work
together. bpdufilter globally disables portfast, bpduguard error-disables
the port. Since the port will be error-disabled, I do not see the advantage
to also disabling portfast.
HTH,
Bob Sinclair
CCIE #10427, CCSI 30427
www.netmasterclass.net
----- Original Message -----
From: Ali AlKaff
To: 'Cisco certification'
Sent: Saturday, April 08, 2006 12:01 PM
Subject: BPDU Guard & BPDU Filter Mutually Exclusive?
I read the Doc, searched the archives and I now fairly understand how they
work. My understanding leads me to think that both features should not be
used on the same switchport. You guys think my assumption's correct?
Another thought is that maybe they can actually work together if they're
configured this way:
spanning-tree portfast default
spanning-tree portfast bpdufilter default
!
interface FastEthernet0/1
spanning-tree bpdugaurd enable
!
end
What do you think?
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon May 01 2006 - 11:41:56 GMT-3