I like your model breakdown of the bugs. Maybe someone smart at Meraki will start doing that!! You do have the second to last MS390 bug listed wrong. Its a 355 bug.
This is a fun one when you are in the middle of an ISE Rollout:
At least it's identified now.
Oops missed that one, as you say, hopefully they'll be sorted at source soon 🤞
I would definitely recommend anyone running 802.1x not upgrade to this version due to
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.
I have an open case. No eta yet but I got asked for more info yesterday and told:
"we have identified some backend issues for this firmware that are likely causing this behavior."
Haven't provided the additional info yet or been able to talk to the tech.
Luckily support was able to roll us back to 14.27 and all our issues went away.
Talked to tech today, he indicated the next stable release was the goal. Didn't give a timeline.
I get the feeling i should delay my upgrade to 14.31 from 12.28.1 set for tonight...
They really should move that bullet point up to the top. This could be very bad for those of us with decent sized ISE deployments. Thankfully, i came here prior to following through 😁
Definitely if you use 802.1x!
It appears 14.32 is becoming available with the relevant fix. Just got a push notice for it for a client. It’s not showing up in all my orgs yet but I think that can be a propagation delay.
I've just pushed the upgrade to the switches where the PoE was on the wrong ports, I'll repost here once applied with the result.
14.32 doesn't fix the 802.1x problem. here's my issue after that upgrade:
agreed. I'm having this issue which isn't due to a mac age out and nothing resolves the problem. I either have to remove the access policy or disconnect ethernet and move user's to WiFi
Any 802.1x users tried 14.32 yet?
We have and despite the various bug descriptions, the 802.1x bug we have with voice vlan clients is NOT fixed in 14.32
@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?
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!
Hey @KRobert ,
Just got confirmation it is a known issue. Support recommended sticking to 14.27.
No update. I haven't really pushed it since 14.27 is working fine for us.
here's my issue after an upgrade to 14.32:
Meraki was able to identify that STP being disabled on ports was causing the 802.1x issue as the switch was not able to maintain an accurate mac table. I enabled STP on all ports where it was disabled and upgraded switches to 14.32 and am having no issues. Dev is reviewing the access policy not working on STP disabled ports in 14.32 as its no an expected behavior
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.
Is there any warning "update before x date" on the firmware page for 14.27? I have my networks on 12.28.1 and 14.27 isn't an option so I'll have to work with support on that. If there is a warning status date, what is it?
No warnings on our firmware page
Hi @bigben386, Can you confirm that 14.27 is still showing "good" in the firmware status?
I just saw 14.33 pop up in the stable rc channel. It says:
Going to give it a go on our beta site.
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.
We updated a larger batch of sites over the weekend. We have not had any issues with our voip phones authenticating after the update.
Great to hear @bigben386 ! Of course they push this version out right after I manually call in to support and update all of my switches to 14.27 😑
Running into similar issue with 802.1x and voice VLANs and 14.32. Just opened a case...
I just saw this Bug Fix with 14.33. Let me know if anyone has any luck with it resolving the voice VLAN authentication issues. @bigben386