I'm glad you bring up the spanning-tree bpdufilter enable command.
There are 2 variations of such command.
1) When used globally, the command is spanning-tree portfast bpdufilter default
2) When used in the interface, the command is the one you mentioned.
Well, the first one removes the portfast status on a port that receives a bpdu while the second command disables the ability to send bdpdus on that port (not good, as this can create loops in a network).
I have seen numerous references to the "removing a port from portfast mode when a BPDU is received" but the manual says simply that it applies bpdufilter enable to any and all ports that are in portfast mode. It also explicitly says the second command overrides the first.
The manual also specifies that spanning-tree bpdufilter enable drops both incoming and outgoing bpdus.
I just checked a recent manual and the behavior is documented there, though poorly -- the verbiage that draws equivalence between the commands is still there, just the actual behavior is described later down in the usage guidelines.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...