06-26-2023 07:27 AM
I am configuring 9200 & 9300 series switches. Do I need to define "spanning-tree bpduguard enable" on each access port or trunk ports? Is it a best practice?
Solved! Go to Solution.
09-25-2023 03:57 AM
very clear explanation on BPDUGuard, do you have similar explanation on spanning-tree guard root?
09-25-2023 04:28 AM - edited 09-25-2023 04:40 AM
To enable it, use the following interface configuration command:
Switch(config-if)# [no] spanning-tree guard root
You can display switch ports that Root Guard has put into the root-inconsistent state with the following command:
Switch# show spanning-tree inconsistentports
Best regards
******* If This Helps, Please Rate *******
06-26-2023 07:30 AM - edited 06-26-2023 07:37 AM
No you need to enable it in all port connect to host not SW'
This port access or trunk.
If you enable it to port connect to SW the STP will blk interconnect between SW.
06-26-2023 07:37 AM
Hi
Enable it on ports you dont want to receive BPDU. For example, if you have a trunk port with your Service Provider but you dont need BPDU from their side coming to your network, that could be a good place.
Only allow BPDU on ports you know you need it.
06-26-2023 07:55 AM
So essentially, we should enable this on access ports where end devices are connected. On switch uplinks it should not be set. Am I right?
06-26-2023 08:01 AM
Correct
06-26-2023 08:16 AM - edited 06-26-2023 08:17 AM
Hello @taro75,
It is recommended to enable BPDUGuard on access ports where end devices are expected to be connected. This helps ensure that only authorized devices, which do not send BPDUs, are connected to those ports.
On the other hand, enabling BPDUGuard on trunk ports is not necessary or recommended. Trunk ports are expected to carry multiple VLANs and can receive BPDUs as part of the normal STP operation. Enabling BPDUGuard on trunk ports could lead to unintended port shutdowns if BPDUs are received on those ports.
09-25-2023 02:22 AM
Thank You.
BPDUGuard should be enabled on access ports. What about spanning-tree guard root? Is it requried to be set on uplink/trunk ports?
09-25-2023 02:25 AM
09-25-2023 02:51 AM - edited 09-25-2023 02:54 AM
By default, BPDU Guard is disabled on all switch ports. You can configure BPDU Guard as a global default, affecting all switch ports with a single command.
Switch(config)# [no] spanning-tree portfast bpduguard default
You can also enable or disable BPDU Guard on a per-port basis, using the following interface configuration command:
Switch(config-if)# [no] spanning-tree bpduguard enable
Best regards
******* If This Helps, Please Rate *******
09-25-2023 03:57 AM
very clear explanation on BPDUGuard, do you have similar explanation on spanning-tree guard root?
09-25-2023 04:28 AM - edited 09-25-2023 04:40 AM
To enable it, use the following interface configuration command:
Switch(config-if)# [no] spanning-tree guard root
You can display switch ports that Root Guard has put into the root-inconsistent state with the following command:
Switch# show spanning-tree inconsistentports
Best regards
******* If This Helps, Please Rate *******
09-25-2023 05:47 AM
Is it always a recommended practice to set BPDUGuard on access ports and root guard on uplinks?
09-25-2023 05:51 AM
Yes...
Thanks
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: