bpduguard & bpdufilter

Spanning-tree portfast (interface level)
        Moves the port directly to forwarding state, skipping listening and
learning

Spanning-tree portfast default (global level)
        moves all non-trunk (access) ports to forwarding state

Spanning-tree portfast bpduguard default (global level)
        Enables bpduguard on all portfast enabled ports, if a bpdu is
received the port is moved to err-disable state

Spanning-tree portfast bpdufilter default (global level)
        Enables bpdufiltering on all portfast enable ports, the port doesn't
send bpdus and if one is received it behaves like there is no bpdufilter
configuration and starts sending bpdus.

Spanning-tree bpdufilter enable (interface level)
        This interface level command prevents the port from sending bpdus
and if one is received it ignores it.

Spanning-tree bpduguard enable (interface level)
        The port sends bpdus and if one is received it is put in err-disable
state. This command doesn't requiere port-fast to be enabled.

In bpdufilter I understand the difference between global and interface level
But bpduguard difference between global and interface level is the interface
level doesn't depends on portfast.

Please someboy to check this

Thanks

Santiago E

Blogs and organic groups at http://www.ccie.net
Received on Sat Jun 06 2009 - 21:19:19 ART