The text states that enabling interface-level BPDU Filter on a PortFast-enabled port prevents it from sending BPDUs, and then suggests that the remote port with BPDU Guard will generally enter the ErrDisabled state.
However, according to Cisco documentation, interface-level BPDU Filter prevents the port from both sending and receiving BPDUs. Since BPDU Guard is triggered when a port receives a BPDU, shouldn't the remote port remain operational instead?
Am I missing something, or is this a typo or technical error in the material?
I'm studying with the CCNP and CCIE Enterprise Core ENCOR 350-401 Official Cert Guide (2nd Edition) and came across a statement about BPDU Filter that I can't quite reconcile with Cisco's documentation.
The book states:
If BPDU filter is enabled on a specific portfast enabled port, the port does not send any BPDUs on an ongoing basis. If the remote port has BPDU guard on it, that generally places the port into an ErrDisabled state as a loop prevention mechanism.
My understanding is that interface-level BPDU Filter (spanning-tree bpdufilter enable) prevents the interface from both sending and receiving BPDUs.
If that's the case, how would the remote port with BPDU Guard ever receive a BPDU and enter the ErrDisabled state?
As I understand it:
- SW1 has PortFast and interface-level BPDU Filter enabled.
- SW1 does not send BPDUs to SW2.
- SW2 has BPDU Guard enabled.
- Since SW2 never receives a BPDU from SW1, BPDU Guard should not be triggered.
I know that global BPDU Filter (spanning-tree portfast bpdufilter default) behaves differently, but the book specifically refers to BPDU Filter enabled on a specific interface.
Am I missing a particular implementation detail or an initial BPDU transmission behavior, or is this a technical error in the second edition?
I'd appreciate clarification, preferably with a Cisco documentation reference.
Thanks!