This hit my company yesterday. Meraki Support acknowledged it's a bug, but they don't have a bug ID or known triggers yet. Looks like it may be isolated to only MS130s, but I'm not 100% certain. We have a handful of switches where this problem exists, they recovered one remotely somehow even though they say part of the workaround/fix is a physical power cycle. I would say stay away from 17.2.1 for the time being. They're recommending for us to use 16.9. Potential workaround/fix that was provided to us: Disabling PoE ports Power off switch Configure firmware downgrade to MS16 Power on switch after 10 secs Wait for the switch upgrade and upgrade back to MS17.2.1 Re-enable PoE port
... View more
