Symptom/Cause | Solution |
|---|---|
STP convergence Interface might be shutdown. Incorrect command syntax BPDU is getting dropped | Use these commands: show spanning-tree Check the Root Id and Bridge ID. Non Root bridge should have the bridge id of the peer bridge show spanning-tree statistics bridge 1 Check the bpdu transmitting and receiving. If receiving is zero means packet is not receiving. In this issue check the port state. Whether its up or down. show interface description Check the interface status. show running-config Verify the whether the command configured successfully. |
Port flapping Might be receiving the superior and inferior BPDU simultaneously Handling of the BPDU is improper | Use these commands: debug mstp all debug mstp cli debug mstp packet rx debug mstp packet tx debug mstp protocol detail debug mstp timer detail |
BPDU sending and receiving Interface is admin shutdown No associated physical interfaces All associated physical interfaces are down | Use these commands: show running-config Verify if the interface is not shut down by the user. show spanning-tree statistics bridge 1 Check the bpdu transmitting and receiving. If receiving is zero, it means packet is not receiving. show spanning-tree statistics interface p8p1 bridge 1 Check the packets send and receive per interface wise. |
RSTP convergence Interface is admin shutdown No associated physical interfaces All associated physical interfaces are down | Use these commands: show running-config Verify if the interface is not shut down by the user. show spanning-tree statistics bridge 1 Check the bpdu transmitting and receiving. If receiving is zero means packet is not receiving. show spanning-tree In the output part please check the Root Id and Bridge ID. A non root bridge should have the bridge id of the peer bridge. show spanning-tree statistics interface p8p1 bridge 1 Check the packets send and receive per interface wise. |
MSTP convergence Interface is admin shutdown No associated physical interfaces All associated physical interfaces are down | Use these commands: show running-config Verify if the interface is not shut down by the user. show spanning-tree statistics bridge 1 Check the bpdu transmitting and receiving. If receiving is zero means packet is not receiving. show spanning-tree mst detail Check the Root Id and Bridge ID. A non Root bridge should have the bridge id of the peer bridge. show spanning-tree statistics interface p8p1 bridge 1 Check the packets send and receive per interface wise. |
RPVST convergence Interface is admin shutdown No associated physical interfaces All associated physical interfaces are down | Use these commands: show running-config Verify if the interface is not shut down by the user. show spanning-tree statistics bridge 1 Check the bpdu transmitting and receiving. If receiving is zero means packet is not receiving. show spanning-tree rpvst detail Check the Root Id and Bridge ID. A non Root bridge should have the bridge id of the peer bridge. show spanning-tree statistics interface p8p1 bridge 1 Check the packets send and receive per interface wise. |
Symptom/Cause | Solution |
BPDU is not handled properly Interface is admin shutdown No associated physical interfaces All associated physical interfaces are down | Use these commands: show spanning-tree This command have bpdu-guard configured a field. If its not showing configured (on) then its not get configured. show running-config Check the configuration of the root-guard. If it showing off means the bpdu guard is not configured. If it configured successfully then upon receiving the superior BPDU the port state will down. Once the port admin goes down then need to bring it up manually. |
Symptom/Cause | Solution |
BPDU is not handled properly Interface is admin shutdown No associated physical interfaces All associated physical interfaces are down | Use these commands: show spanning-tree This command have bpdu-filter configured a field. If its not showing configured (on) then its not get configured. show running-config Check the configuration of the root-guard. If configured successfully then upon receiving the superior BPDU the bpdu-filter configured port will loose its bpdu-filter and it will become normal port. |
Symptom/Cause | Solution |
BPDU is not handled properly Interface is admin shutdown No associated physical interfaces All associated physical interfaces are down | Use these commands: show spanning-tree This command have root guard configured a field. If its not showing configured then its not get configured. show running-config Check the configuration of the root-guard. On receiving superior BDPU then root guard port should move to the root-inconsistent. If its not behaving like this then handling of the packet is improper in the control plan. |