Community Record
2
Posts
0
Kudos
0
Solutions
I did a packet capture once only when a client reported login problems at a particular spot in the building which sounded unusual to us. There I noticed that the device was trying to link to an AP working on a channel we never use (153). We need all the channels there are due to high density, but 153 and 149 are used by apple tvs so we avoid them. We have lots of Apple TVs in a school setting. To check DFS events you can go to meraki dashboard, Network-wide, Event log, Event type (include). There you filter out the event-type you need (DFS). A problem that can happen here is that if the event happened too long ago, then the history will return nothing. But the catch is if you compare what channel the AP is actually working on versus the channel you have set it if you have set it manually. You can open two pages, one with the APs that includes the Channels Column and the other with the channel settings and look for mismatches. By the way, I use the old version. Our engineer is preparing a script to do it automatically but has found some limitations with Meraki API at this point.
... View more
Check DFS events. If your channels are not set to auto, check to see if the AP's are operating on the channels they are actually set to work. MR46 has a "known bug" where AP's changing channels due to DFS don't return to the original channel therefore they may cause co channel interference. We are dealing with the same problem and waiting for Meraki go fix the bug. Rebooting the AP corrects the problem.
... View more