Absolute Bevy of Fixes, including I believe Voice Vlan/802.1x and layer 3 changes needing a reboot.
>SVI changes made to stacks may result in incorrect route mappings resulting in packet loss (present since MS 14.32)
I got bit by this one today. I deleted a VLAN on an MS225 and had to reboot the switch to get routing working properly again.
I am hitting this one again and again with most customers. Some will move away from Meraki because every route-change needs a planned maintenance window.
I've had two customers with recurring occurences of this bug. One of those is a big one (for my scale) and he wasn't happy with the 'unstable behavior' of his MS425's.
Interesting to see that it is not just the 35X series as I thought before. I only had this on lots of these devices and not on 2XX and 425 switches.
Hey guys, this is a little disheartening and scary. My environment is currently on MS 12.14 and Meraki auto-scheduled an upgrade to 14.33. I was initially going to hold off, but now I'm planning to upgrade during our next maintenance window because we're starting to see a weird issue (again) where our Thin Clients that are connected to an MS350 Switch Stack running Layer 3, get randomly disconnected from their remote VM sessions without any rhyme or reason. (When users connect to these same VMs from home, this doesn't happen). This used to happen to us on MS v11 (never occurred when we were on MS v10) and I thought MS 12.14 would solve it (upgraded during the pandemic), but I guess we didn't see the issue resurface since very few people were actually in the office during the height of the pandemic. Now after seeing these posts and also seeing some of the release notes for the 15 code with "Known Issues" similar to this is starting to make me worry. I'm not sure if this is the same issue that I'm facing, since I haven't made any recent changes to any SVIs, but it sounds similar to what we're experiencing.
The issue that we're actually facing is closer aligned to this: https://community.meraki.com/t5/Switching/RDP-Brief-Disconnects/m-p/113785/thread-id/8228
The question is, what do we do??? These kind of routing/disconnect issues seem to be pretty longstanding and have been around for much longer than Cisco Meraki should even admit without feeling ashamed. I don't even know how this product could be greenlit for production at this point with all of this instability. I'm starting to be afraid to even run these Switches in our environment right now and we've got quite a few sites running these Switch Stacks in production (still have to survey the other sites, as we begin to return to office). I don't know which Firmware version to go to...I'm just at a loss right now.
This was a bad one. Meraki had multiple versions of this issue and I worked closely with Support in our LAB to help them gather data. It was affecting MS425 stack and stand-alone. They even had me test with a custom build to confirm their fix was working. At least in our environment, 14.33 did fix these abnormalities including our MS390 control plane issues which drove me crazy.
Hmmm...and this is coming from a Meraki employee...so what I'm hearing from you is to probably Not upgrade to 14.33 in a couple of weeks?? Is that correct @Make_IT_Simple ? Is there any Firmware version that is the most stable that you guys would recommend? I appreciate your response in advance. Thanks
Sorry about that @Make_IT_Simple , I misread your post. It looks like you're saying that in your experience, 14.33 did resolve these issues in your environment, is that correct?
My apologies for misunderstanding, if that's the case.
Does anyone with 390's and L3 on it install this yet? and is it an improvement from 14.32?