I was trying to understand bpduguard, I put fa0/1 on SW1 as spanning-portfast, never went down. I put bpduguard on int, never went down, I sh/no shut the int and got this:
*Mar 1 01:39:21.943: %SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port Fa0/1 with BPDU Guard enabled. Disabling port.
*Mar 1 01:39:21.943: %PM-4-ERR_DISABLE: bpduguard error detected on Fa0/1, putting Fa0/1 in err-disable state
Why did it take a sh/no shut to bring about this error?
While it was a trunk, it wasn't an access port. You added portfast after the fact, then added bpdu guard. BPDUGuard doesn't work unless the port is operationally in portfast mode (which isn't usually the case for a trunk). When you shut, no shut the port, it initially came up in portfast. It would lose its portfast status when it receives the first BPDU. But this time, BPDUGuard is enabled, so it would err-disable the port instead.
hi guys, I have the same problem on the f0/1 port gets disabled when i connect an access point, is there away in which I can prevent this from happening and also keep my port on PoE?
What kind of Access Point? Cisco?
These are some basic commands I have used for AP's (and then add qos).
switch(config) interface f0/1
switch(config-if)# switchport trunk encapsulation dot1q
switch(config-if)# switchport mode trunk
switch(config-if)# switchport trunk allowed vlan xxx, xx
switch(config-if)# spanning-tree portfast trunk
BUT, I have never applied bpduguard to an AP.
bpduguard is suppose to errdisable the port if it gets bpdus.