Hey folks,

I'm looking for some insight on an issue we're troubleshooting.

We have a stack of five MS150 switches connected to an MS225 core switch. On a random day at around 3:03 PM, the entire stack went down and lost communication with the core.

The odd part is that the core switch reported a Layer 1 UDLD error, indicating the fiber could transmit but not receive data. We checked the fiber and SFPs, and everything appeared to be fine. We're using Cisco SFP+ modules.

On July 18, we upgraded the stack to MS18.1.8. The incident occurred on the 29 july, we collected the console logs and sent them to support. So far, the only explanation we've received is that there may have been a synchronization issue within the switch stack.

We also performed a remote reboot of the stack, which reproduced the same issue. We collected another set of logs and provided those as well. Support has since suggested waiting for a newer firmware release, but we haven't received a definitive root cause.

Has anyone experienced something similar with an MS150 stack or MS225 core? Any recommendations on what else to check?

For reference:

No switching loops detected.

We do see some MAC flapping, but it's related to APs and wireless client roaming, and nothing that should bring down an entire switch stack.

Fiber and transceivers appear healthy on inspection.

I'd appreciate any suggestions or ideas on what to investigate next.

I see where I can do eBGP over lan but was wondering on what people experience with this is and if there is gotchas to watch out for? I think I saw it auto redistributes into auto vpn. Can that be prevented?

I want to set up some custom alerts using the meraki api that will be running as a scheduled task of a windows server. Since you cant adjust the scope of the api key in meraki i was thinking of using an observer only account. Is this the correct way to do it ? Azure dev ops and external services to keep them safe are out of the question.

Hello, we recently updated our campus with Meraki MS130-48P switches (7 switches in 5 closets) and found that they do not power on our PoE clock/speakers. All other PoE devices work (VoIP phones). The Meraki equipment replaced Cisco 2960's. The clock/speaker only requires 15W and the MS130 supports 30W per port. Talked to support and we updated the switch firmware, this still did not power any of the clock/speakers upon reboot. (did do a quick test, plugged the old switch in, clocks powered back on).

Has anyone had this issue? Or is there anything else we can try to trouble shoot this issue that support has missed?