I think there have been a lot of cases opened regarding this issue and no one is seeing any real help other than upgrade, which was actually the wrong thing to do. I have sent several packet captures in monitoring mode and from the APs but no one was able to help from support. The only real help came from this thread. So suggesting that we open a case and work with support is not real helpful at all. Now I do not know when i could actually upgrade again because MEraki seems absolutely incapable of clearly identifying the issue that only started once we upgraded to MR29 code in high density environment. And what was introduced with this code? New form of client balancing? Interesting. ... View more

I feel like rolling back to MR28.7.1 was successful but need to monitor some more. Today was not as populated as last week but enough to say that we did not have any user go into the excess frame loss sunken place. I also stopped getting some awful association issues with the phones on the network. I still see the excess frame loss messages in event logs but like I stated before this is not an indication that there was an issue. Overall I am seeing way less disassociations due to excess frame loss. If you want to roll back to this version you will need to call in to the TAC and have them schedule it. I would say read the release notes first. I upgraded from MR28.7.1 to avoid layer 3 issues with sticky anchors so I felt confident with the downgrade since I removed layer 3 routing from my environment. Good luck!     ... View more

can you elaborate more about what you are seeing with DFS events? were you able to capture any of this in monitor mode? I always see some DFS event being right next to a large river but I am not certain of the affects on users. are you using auto channel or static? my understanding is that auto channel rules should apply after the DFS event. ... View more

We finally pulled the trigger and asked Meraki to roll us back to 28.7.1. Now we sit and wait. Today is one of the busier says of the week with people moving for meeting room to meeting room so lots of roaming and chances to end up in excess frame loss wormhole.   ... View more

Upgrading to 29.5.1 did not resolve the issue. I feel that whatever this issue is it started with 29.4 though I never really upgraded to this and went from 29.8.7 to 29.5. At the time I was trying to fix issues I was having with layer 3 roaming so I was not thinking about this issue specifically. When layer 3 roaming still seemed to be a problem I removed it from my environment completely. That's when I started noticing the issue that was probably already there hiding behind my hatred of layer 3 roaming.  I am thinking of returning to 28.7.1 now. I really feel this has something to due with the new Client Balancing feature that was launched with 29.1. I upgraded off 28.7.1 because I thought that layer 3 roaming might improve so now that it is removed maybe it will stabilize the issue. What I do not understand is why Meraki refuses to admit this is a real issue. ... View more

wait how do you turn off client roaming? Do you mean client load balancing or client steering? To my understanding that the new version client balancing released with MR29.x is active.The new active client balancing technique has been introduced in MR 29.X firmware, where an AP would try to steer already associated 802.11v-capable clients to a better AP (if one is available) using BSS-TM frames.   When I read this I feel like this might be related to the issues we are seeing. So If I understand what you are saying is that you allow the clients to drop connections between floors and reassociate when they arrive on another floor. This makes me believe that you are doing a layer 2 roam between broadcast domains and might be turning off layer 3 roaming. I did the same because layer 3 roaming in Meraki is a complete waste of time. ... View more

 A week ago we upgraded to 29.5.1 but last week we had a low number of users come into the office and experienced none of the sudden traffic drops but still saw the excess frame loss messages in the event logs. I suspect this week might have more traffic and I can determine the affect of the upgrade but I am not feeling hopeful.  ... View more

were you running 29.4.1 and rolled back to 28.6? was this the advice of Meraki techs? I was on 29.5 and seemed to be getting the same negative affects but they suggested I go to 29.5.1. I finally upgraded over the weekend and I am monitoring results. i do not think just seeing the excess frame loss message indicates an issue. there seems to be another factor that I have yet to find. to me the new client load balancing is more suspicious given the fact that is is on by default and there seems to be no way to disable that. today is usually a crowded day so the firmware should get tested.  ... View more

I think I experienced this issue first hand:   This happened as I came back to the office today from working from home since 1/25/23. My laptop was connected to an AP and had an IP address but could not ping the default gateway or traceroute out. I tried to turn off my wifi adapter but could not. I was able to put my adapter in sniffer mode as per the monitor mode packet capture instructions. After I ended the capture my laptop seemed to have even more issues. At one point all the adapters listed in System Preferences>Network disappeared and I had to reboot to recover. I was able to recover the .pcap and forwarded it to Meraki.   I am running macOS 12.6.2.   ... View more

I am also seeing similar issues however I am running MR 29.5. I upgraded because of issues with layer 3 roaming. Support suggested that we go to 29.4.1 but around the time we opened the ticket they told us to skip that version and go directly to 29.5. This was because the same damn layer 3 roaming issue persisted on 29.4.1. I checked my logs and was seeing these disassociations during the time I was busy trying to fix layer 3 roaming. We got sick of the layer 3 roaming issues and moved to one broadcast domain. Now that we are layer 2 roaming it has been apparent that there are other issues with roaming and that led me to check the logs going back 2 months when we moved to this version. We upgraded December 1, 2022. So I now see they have 29.5.1 available but no mention of this issue being resolved as well as no mention that the layer 3 roaming anchor "stickiness" being fixed. I am at a loss and getting really pissed. ... View more