I have a test lab network that I created that contained 3x MS350-48FP switches that I had physically stacked. I had finished testing and the stacking cables, etc were disconnected and placed on a shelf in our storeroom for about 7 months. I needed to use one of these switches in our production network today, so I removed the stack in the dashboard and moved one of the switches into the production network. I connected the uplink and it will not reach the cloud, which made sense since the uplink in the test network was in a different vlan than prod network. I connected a laptop, went to 1.1.1.100 and into the local device page. I change the uplink config to use DHCP and entered the correct vlan and clicked save. Still no connectivity to Meraki cloud. I checked the port status tab and uplink is connected at 1gbps to an upstream meraki switch that has connectivity to the Meraki cloud. If I plug a laptop into the cable I'm using for the uplink, I get a dhcp address on the expected network and can browse the web, ping meraki cloud IP's, etc. I confirmed the port on the trouble switch was a trunk allowing all vlans. I also tried it as an access port in the uplink vlan and still no connectivity. I've factory reset the switch about 5 times now, even cycling the power a few times too. The local device page is retaining the correct uplink vlan and ip settings. I've also tried a static ip in the prod vlan.
After all of this, I called Meraki support and advised the things I tried. We tried the factory reset, dhcp, static ip steps again just in case there was something I may have missed, and the tech decided it was a bad switch and kicked off an RMA about 30mins ago.
So I went and grabbed one of the other switches that was previously in this stack, and repeated the steps above and same issue. I find it hard to believe that the 2nd switch is also bad. I am bout to go and try the 3rd switch that was in this stack.
Wondering if anyone has experienced a similar issue, and there's maybe something I've missed?