Hi Bodnar, Using the 'spanning-tree portfast bpdufilter default' command it will cause portfast to be disabled if a BPDU is received on the port. If it's issued at the port/interface level with the 'spanning-tree bpudfilter' command it prevents a port from sending or receiving BPDUs.
If you've issued the 'spanning-tree bpdufilter' command on a port, bpduguard won't work on the same port, as the filter takes place first and guard never sees it. I've never tested the 'spanning-tree portfast bpdufilter default' method, but since it's function is a bit different in that case they may play well together in that configuration BR. --- On Sat, 7/31/10, Bodnar, Edward <[email protected]> wrote: From: Bodnar, Edward <[email protected]> Subject: [OSL | CCIE_RS] Can anybody help me out soem To: "OSL Routing and Switching" <[email protected]> Date: Saturday, July 31, 2010, 10:27 PM Very simple topic but I keep getting turned around on this. Does anybody have a link that can clear up what the difference are? I know potfast no problem. And bpduguard and bpdufilter seem to make sense to me. But starting to use them with the default option and I start to get cloudy. Spanning-tree portfast Spanning-tree portfast bpduguard Spanning-tree portfast bpudfilter Spanning-tree portfast bpduguard default Spanning-tree portfast bpdufilter default -----Inline Attachment Follows----- _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
