STP - Stopped receiving BPDUs with loop guard enabled

Sweemz
Here to help

STP - Stopped receiving BPDUs with loop guard enabled

Hi All,

 

I hope we are well.

 

I’ve recently inherited a Cisco Meraki network following an acquisition and have noticed some alerts.

 

Edit - Added Network Topology/Switch overview (below)

 

Toplogy

Sweemz_0-1737623756757.png

 

Switch Overview

Sweemz_1-1737623942455.png

 

 

Sweemz_0-1737580717988.png

 

The network Consists of:

2 x MX105 in HA config.

5 x MS130-48P 

4 x CW9166I


I've documented the network as best as possible..
(minus the access points) will re-review tomorrow and update asap.

 

Version 1

Sweemz_1-1737580780911.png

 

Version 2 - Since Reviewing Meraki Live Topology

- Root Ports mislabelled / corrected 

Sweemz_0-1737625704971.png

 

 

DUG00-SW01 Port 51 

Sweemz_2-1737580917103.png

Sweemz_3-1737581077005.png

 

DUG00-SW03 Port 50

Sweemz_4-1737581257527.png

 

Sweemz_6-1737581286390.png

 

The affected ports seem to be alternate uplink ports, so the network is still operational. I’d just like to understand the issue and get the network’s RAG status back to healthy.

 

Any thoughts on the best place to start troubleshooting?

 

Thanks in advance - let me know if you need more information!

 

9 Replies 9
RWelch
Head in the Cloud
Head in the Cloud

I realize you mentioned inheriting this network but the device health notice indicates SW01 and SW03 error notices yet the lower images you share indicate SW04 and the port descriptions don’t seem to jive.  Seems like something doesn't quite add up.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
RWelch
Head in the Cloud
Head in the Cloud

Can you share a screen capture of the topology from the meraki dashboard to see what that shows....I'm curious to see if that might reveal more insight.  Not meant as critical at / toward you....just tried to understand the above and I looked at it like 10 times.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
IvanJukic
Meraki Employee
Meraki Employee

Hi @Sweemz ,

 

Not sure I follow the Topology Diagram either. Port 52 is directly connected to the Root switch. So that would be the Root port. Port 49 & 50 would be alternate ports.


I agree with @RWelch. The Topology map in the Dashbaord is 'live". So if the Tree changes so will the map. I use it daily. Best tool to use for these kind of queries.

 

https://documentation.meraki.com/MS/Monitoring_and_Reporting/Network_Topology

If you can share a screenshot, that'll be helpful.


Cheers,

Ivan Jukić,
Meraki APJC

If you found this post helpful, please give it kudos. If it solved your problem, click "accept as solution" so that others can benefit from it.
Sweemz
Here to help

Hi @IvanJukic 

 

Thank you for looking into this.

 

2nd glance i've clearly made some mistakes with my labels 😅

Using the Network topology tool I have re-confirmed the uplinks/ports and updated my documentation to reflect the live links in the Meraki Toplogy.

 

Sweemz_0-1737625324266.png

 

 

Sweemz_1-1737625371887.png

 

Sweemz_2-1737625385422.png

 

Sweemz
Here to help

Not sure why I didn't include these originally 😅 .. Thank you for looking into this btw

 

Toplogy

Sweemz_0-1737623756757.png

 

Switch Overview

Sweemz_1-1737623942455.png

 

RWelch
Head in the Cloud
Head in the Cloud

Not sure why 3 downlinks are needed….seems a bit overkill or over engineered.  

 

Too many redundant paths likely intended for a failover situation but the errors seem to be the redundant paths (3 downlinks).

 

If it were my network to remedy, each switch would have only two downlinks with all root traffic from SW00.


SW01 and SW02 would be one alt path (loop guard)

SW03 and SW04 would be one alt path (loop guard)

 

I would remove the link between SW02 and SW03.

I would remove the link between SW01 and SW04.

 

Thanks for sharing the topology to better understand. 
That would be my suggestion/recommendation. 

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Sweemz
Here to help

Thank you @RWelch 

 

Makes absolute sense.

 

I'll have a play with this network this evening and provide an update on the topology asap.

RaphaelL
Kind of a big deal
Kind of a big deal

APs do not participate to the STP topology so that shouldn't matter 

annmarie24us
Meraki Employee
Meraki Employee

I agree with RWelch too many redundant paths for the failover situation and the errors do seem to be the redundant 3 paths.  

 

I see you are on MS 16.9 and there is an update firmware for these switches as well MS 17+ would help as well.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels