MS355-48X switches drop after adding to stack

[Robert1974]

I updated one-by-one each of these ms355's yesterday to ensure they had the proper firmware. today, powered them up one at a time moving the lan cable to each one once i ensured the firmware was still current.

I powered them all down. I stacked them using MA-CBL-100G-50CM cables in the ring as per Meraki best practices.

The one connected to the LAN ethernet cable came back. its partners did not. All but switch-1 has an amber light and is viewed as "unreachable" in the dashboard. The DHCP that delivers them IPs' is coming off a brand new MX105 that is connected to the lab lan cable. The MX105 gets its ethernet WAN configuration fine. It sees our preferred DNS (cisco umbrella), and it is dishing out DHCP on the Native VLAN. The switch that is connected by ethernet to a LAN port on the MX105 is able to see the dashboard. none of the other stack members can.

[Ryan_Miles]

I recommend you open a Support case so they can take a look

[Robert1974]

thanks, already did. figured id keep working on it and see who knows something that i didnt while i wait.

[gardn8]

Did Meraki ever figure out the root cause? I am currently experiencing the same thing and all they have told me is "That isn't supposed to happen". 

[gardn8]

Any chance you are able to look into this more? I am having this same issue and all support has told me is "that shouldn't happen". I was also told the fix that cmr posted below is not expected behavior (although it works every time we have powered the stack down for testing). 

[Brash]

Did you factory reset them after the upgrade?
I don't know if this is required but it's possible they're still expecting a local uplink to connect to the dashboard (as per their last configuration).

[cmr]

We find that you should have each connected to another when you power up like this to enable the initial stack forming.  We normally have switch 1 to internet switch 2 to switch 1 on a front port that is trunk native VLAN 1, switch 3 to 2 etc.  Soon after powering them all up the front port inter-switch links will start blocking and you can remove them.

[Norman3]

So let me see if I get this right.. The Switches are stacked. They have a 100G link between them on the Stack cables, but somehow this translate to, I need a 1g link on the front in order to get to the dashboard? How STUPID is meraki, that it can't use the stack link as.... a STACK LINK!?!?!? We have been dealing with this same stupidity since we started using these switches. Just an FYI, it is because these idiot stack link ports are being shut down by Spanning-tree. This is an issue on previous stackable switches as well (WHY?) but at least on those, you could turn Spanning-tree OFF.. This, evidently was not generating enough support tickets for Meraki support so they decided in their Infinite wisdom to remove access to be able to turn spanning tree off on the stack ports.. so yeah, If you use these switches in a stack, and lose power to them, you will 99% of the time break your stack up until you go in and physically connect an uplink port between the switches.

C'mon Meraki.. Get your crap together. When switches are stacked, they are stacked. They should only be one switch. The Stack ports should not be treated like regular ports, they should be backplane links. Above all else they should NOT be able to be shut down by something as dumb as Spanning-tree.

[Norman3]

I just noticed this post was a year and a half old... Meraki still hasn't fixed it.. Guess this is insanity by design..