Re: bpduguard question

For the command you are referring to there is a relationship between
portfast and bpduguard (spanningtree "portfast bpduguard" default ) ,
it means if i receive any bpdu on a portfast enabled port then the
port is shut down cos it expects workstations and servers to be
connected to that port , so the command is "activated or begins to
listen for bpdu's " when there are portfast enabled ports .
But the interface level spanning-tree bpduguard enable has nothing to
do with portfast , it instructs the switch to shut down the port where
it is enabled if any bpdu is received whether or not portfast is
enabled on that port.

HTH

On 9/10/09, Erik Witkop <ewitkop_at_gmail.com> wrote:
> Entered globally:
> Spanningtree portfast bpduguard default
>
>
> I have a few questions about this command. When the command is entered,
> it seemingly has no effect. But once you turn on portfast on the
> interface level, BPDUguard is now working.
>
> What does bpduguard have to do with portfast? It seems that they are
> two separate technologies.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Warm Regards
Peter.
Blogs and organic groups at http://www.ccie.net