Just a quick question to clarify my mind. If you enable portfast globally, bpdu filtering and bpdu guard is disabled, if i'm correct. So portfast basically will turn the port into normal stp port if it receives a bdpu on a port; it will also send bpdus. Am I correct on these?
If you configure bpdu filtering globally, then the only behavior that will change is that bpdu will not be send from the portfast configured port. Am I correct here also?
I've read few sources that seem to be contradicting each other and wanted to make sure by asking someone.
With portfast, the port still run spanning-tree, so indeed may send, receiver or process BPDU. But the only difference with a normal is that in the spanning-tree state machine you bypass the transition listening/learning/forwarding to go directly to forwarding without any further check or waiting time.
with BPDU filtering you drop any receive bpdu on port where it runs and you do not send any. this is not recommended except on some port where there is a clear design goal for it. You typically do not want to run bpdu filtering on a port where an end hosts runs as it may very easily introduced loop.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...