The issue is more Catalyst switch management was "coming soon" nearly 1.5 years ago. The MS switch lineup has serious fragmentation issues and the MS130 isn't solving it. ... View more

I really wish they would just support catalyst 9200s. The Meraki switch lineup makes no sense and the MS130 does not help. It is better than most MS2xx models but missing one or two key features of those lineups. ... View more

Well that is unfortunate. This would be the perfect AP switch with it since there are no MS2xx with mGig. ... View more

Will the MS130 support SecurePort? ... View more

Yeah it is really disappointing. They announced C9300 management a year ago with more to come but still no other switches have been added. The MS series is annoyingly fragmented and ridiculously priced. I remember when Meraki switches were affordable.  ... View more

So this means we will soon be able to manage C9200 also? 🤞 ... View more

Have you tried enforced .11w and transition mode with 29.5? ... View more

We are also seeing .11w issues with 29.4.1 on transition mode networks with enforced .11w. ... View more

@EJN  please keep us posted. I saw that 15.12.1 showed up as a new stable fw in our account and wanted to see if anyone was brave enough to try it. Sound like Meraki needs to adjust their criteria for marking switch firmwares as stable. 14.31 was a stable disaster for us. ... View more

We updated a larger batch of sites over the weekend. We have not had any issues with our voip phones authenticating after the update. ... View more

So far everything has been working fine on our PCs connected through the voip phones. We haven't had too many people in our beta office so far this week though. ... View more

I just saw 14.33 pop up in the stable rc channel. It says: Bug fixes The Voice VLAN fails to stay authenticated if it is authenticated before the Data VLAN (present since 14.28) Going to give it a go on our beta site. ... View more

No warnings on our firmware page   ... View more

No update. I haven't really pushed it since 14.27 is working fine for us. ... View more

We run STP on all our access ports and had issue on the voice vlan with 14.32. I would recommend anyone doing 802.1x on their voice vlan to still stay on 14.27. ... View more

Hey @KRobert ,   Just got confirmation it is a known issue. Support recommended sticking to 14.27. ... View more

I have opened a ticket with meraki about this. Looks like 14.32 fixed the issue for the data vlan but our phones on the voice vlan are disappearing from the switch's mac tables just like data vlan devices did in 14.31. Rolling back to 14.27 again! ... View more

@Mloraditch We just tried it too and we are also having issues with the voice vlan. The bug mentions mac whitelist but we are not doing that. We use 802.1x for voice vlan authentication. Are you doing similar? And do you have a ticket open with them? ... View more

Yes they all need to be enabled in the poly config for devices behind the poly to function properly. It helps inform the switch when devices connected behind the poly change. ... View more

Did you make sure you are sending the radius attribute noted in the config guide?   Multi-Domain With multi-domain authentication, one device can be authenticated on each of the data and voice VLANs; if a second device is detected on one of the VLANs, the device will not be granted access. In this mode, Hybrid Authentication is used and Voice VLAN authentication is required.  This mode is recommended for switchports connected to a phone with a device behind the phone.  Authentication is independent on each VLAN and will not affect the forwarding state of each other. Cisco Meraki switches require the following attribute pairs within the Access-Accept frame to put devices on the voice VLAN: Cisco-AVPair device-traffic-class=voice ... View more

Any 802.1x users tried 14.32 yet? ... View more

Definitely if you use 802.1x! ... View more

Luckily support was able to roll us back to 14.27 and all our issues went away. ... View more

I would definitely recommend anyone running 802.1x not upgrade to this version due to Clients on a RADIUS authenticated port that ages out of the MAC table due to inactivity will fail to be relearned until a port bounce has occurred (present since MS 14.28) That is killing us. Phones and printers are becoming unreachable due to this and it only takes a few minutes of inactivity for them to age out. Very frustrating. ... View more