@jimtombari2 this firmware is not the same as that for the Go range. I suspect the Go release could have something in common with the issue fixed here that was in the 15.20 release...
current firmware is 15.21 - that is the firmware that is causing the issue in multiple locations.
It was set to update on Sunday at 4am but most places having this problem appeared to start having it within the last 8 hours or so, the firmware says GS 15.21 so it looks like there is a major bug in it.
Hi all - for anyone using Meraki Go, and still encountering PoE issues with their Meraki Go GS110 PoE switches, we found a workaround to the firmware issue.
More details in this thread in our Meraki Go Community: https://community.meraki.com/t5/Questions-and-Answers/Meraki-Go-PoE-Switches-Resolved/m-p/188466#M14...
Note: Meraki Go is a completely different product line than our Cisco Meraki products 🙂
This announcement: MS 15.21 Stable (GA) is available for install!
...says that MS 15.21 introduces port isolation under "new features".
But then links to this old article :Restricting Traffic with Isolated Switch Ports
Firmware MS 11.22 adds support for Port isolation on the following.
- MS Switch Stacks
- All ports on the MS210, MS225, and MS250 series switches. Prior to MS 11.22, these switch models supported Port isolation on ports 1 - 24 only.
But that same article as recently as October 2022 use to say:
For MS210, MS225, and MS250 series switches, port isolation is only supported on the first 24 ports
Port isolation is not supported across stack members
Back in October 2022, MS 11.22 was ~3 years old.
Colour me confused by the mixed messaging! 😕