Am I last to find out that Meraki Go switches run the same firmware as "regular" Meraki? Now I wonder about the Go GX firewall and GR wireless..
Lol, no I only found out with the 15.21 release... I'd guess there is a good amount of commonality in all of them.
On another note, this known issue was added to 15.21 and remains in 15.21.1 which could be a bit alarming as a lot of DHCP devices show 0.0.0.0 before getting a real IP, hopefully it doesn't mean that! Also when you connect a Meraki AP it often hunts around the VLANs, especially if it was static on VLAN n and is now set to DHCP with a different native VLAN on the trunk to the port.
MS390 SNMP ifIndex integer offset starts at 9 instead of 1
This is mentioned in 15.6 as fixed but I can confirm this is an issue on 15.21.1
With a stack 2* MS390-24:
First switch first port starts at 9
Second switch first port starts at 53
With a stack 6x MS390-48P
Firmware updated this noon -> tonight the entire stack is unreachable from the Meraki cloud... amazing...
All other switch (MS350, MS220) are ok...
Updated to this release this week. After upgrade, all switches with DHCP relay configured over WAN would not allow clients to connect to the network. Previous 14.33.1 worked fine, does anybody know if this is a known issue? I haven't downgraded yet, simply unblocked the local Routers DHCP server in Dashboard.
Anyone else having an issue with MAB authentication? All of our devices using MAB are getting the following error: "RADIUS server returned an invalid VLAN name". I confirmed that it's the correct VLAN being provided by the radius server and it only started occurring after the upgrade.
Only this version or any version from the MS 15 branch ?
I'm not aware of any issue with MAB currently sorry.
So all my networks are on 14.33.1 and I was looking at upgrading to 15.21.1 and did some community searches and found several red flag discussions with people reverting back to 14.33.1. I'm not in any rush so I'll hold off, but it seems like 15.21.1 is causing issues for people. Thoughts?
We have it deployed on various networks with 355s and some with 225, 220, 210 and 120 models. Seems okay to us, but we don't use DHCP relay and don't have 390s.
Make sure to re-test your Group Policies. Seems that some behavior might have changed ( like DNS/DHCP were always implicitly allowed , might not be the case now ). I have to do more testing about that.
Using it with MS425, 225 and 120 switches and apart of upgrade not going very well the devices seem to work just fine (no rollback done or so).
DHCP relays 802.1x, SecurePort all work correctly, didn't notice any POE issues as some reported.