@NolanHerring  get a refund lol ! ... View more

@NolanHerring  It's in the doc Phil linked further up under number of devices per network   Number of Devices per Network The number of Meraki devices (MX, MS, MR, MV, etc., not user devices) per network is a much more variable number that does not have a general recommendation. It will vary from case to case. Note that there is a limit of 1000 devices per network. Networks exceeding this number should be split. However, it is generally uncommon for networks to approach this number unless they have a very large number of cameras or wireless access points. If this is the case, it is recommended to split the networks based on physical areas or use cases. ... View more

Perhaps they are referring to the 1000 access point limit per network (as opposed to the 25k limit per organisation).  Although best practice for autoRF would be not to have that kind of number in a single network (unless of course that was one (BIG) single geographic location) ... View more

If you are uncomfortable running beta or 'stable release candidate' firmware (i.e. 26.6) and are having this issue, just log a support call so they can apply the option on your dashboard for your network(s) for you to schedule a roll back to 25.13 (or whatever version works for you) ... View more

Was considering moving from 25.13 to the latest 'stable' 25.14 version...   Random disappering SSiD's ?  Think I'll pass.  ... View more

MR18 is not an old model, end of sale was only 2017.  It's bugs like these (if it is as a result of a bug introduced in new firmware) that worry me, and with end of support at 2024 for this model we shouldn't have to bin these older models or have them firmware locked.  I still have a few MR16's, again firmware locked because of a bug introduce in 25.x   I hopeful that the firmware release quality control improves significantly in the future ... View more

@NolanHerring  I agree entirely that the fine tuning of channels should not interupt clients when an AP has a large number of active clients, however, would it make the same decisions at say 8am or 6pm when the number of clients and client utilisation/interference is low ?  Surely the best fit decisions it makes are based on the high channel utilisation/interference when the AP's are busy during office hours.   Ideally, it would remember the findings during the day, draw up an optimised plan and implement out of hours.  It would then analyse the perfomance the next day (when busy) on those changes, compare with previous settings, and fine tune further if needed (and apply new plan again out of hours)   Nice article explaining autorf here, which I think Nolan may of already found   https://wirelesslywired.com/2019/05/08/meraki-auto-rf-explained/     ... View more

@MichelRueger  Yes, good call, I missed the schedule option, but I don't think that'll do what you need as the client can only be in one group policy at a time, so if they try to access the internet when the time schedule is set to off (for the policy they have been assigned), they won't get any access, as the schedule is off. You need to be able to toggle clints between 2 different policies,....Sadly, I think API scripts is the only way to be able to do that   Scrub above, testing shows that when the time schedule is off for the policy (i.e. that allows P2P) then the client is assigned 'normal' access (no policy) and the default settings (i.e. no P2P) for the SSiD is applied, so @MichelRueger , yes your solution will work ... View more

You can create a group policy to allow access to torrent sites (and another policy to block), change the SSiD firewall settings to allow/block L7 rules for Peer to Peer access.  You can turn on SSiD's using SSiD availability and time bands.  But, I don't think you can do both other then having one SSiD available at certain times (which allows torrents), this then turns off and a different SSiD that blocks torrents comes on line when the other goes off within the dashboard itself... You could run API script(s) to move the clients from the allowed (P2P) policy to a block policy at different times of the day (and then back again), that way the policies would apply to a single SSiD and I think this would do want you want it to do ... View more

It can most likley be done using API, but you could use the configuration sync option to copy the ssid with the desired traffic shaping policy from the source network to the destination and then rename the SSiD (and change any other settings), although depending on your config might be more work doing this (good if the SSiD's are the same) ... View more

This is a useful article   https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Wireless_QoS_and_Fast_Lane ... View more

@GJ1  Good work, if thats the case then it's not Meraki related.  Get back to basics, get some pings going to the IP's of the affected access points from both sides of your firewall (internal lan and external sources), if you are seeing drop outs then it's no wireless/radio/client issue.  Repeat the pings to hardwired devices at the site, printers, servers etc.  If you narrow it down to a general network/firewall issue check things like switch port duplex/speed mismatches, broadcast storms (loops on network), routing etc   Good luck ... View more

Yes, take your time, get back to the same config prior to the issues, don't wildly make changes like DNS etc. Take a breath and as @Nash  says gather as much reconnaissance as you can to see if there are any similarities with clients, access points, radio band, time of day, client type ect for those working and those having issues   Once you have narrowed it down it'll be easier to diagnose.  Even though you said the issue started before you upgraded the firmware, if you have been running 25.13 for many months (that version is nearly 12 mths old) in your enviroment without problems, at least by going back to that will ensure that there are no new variables to worry about   Good luck ... View more

@GJ1  wrote " We did a firmware upgrade last Thursday "   ROLL BACK FIRMWARE   The bulk of our AP's are MR32's and 25.13 is solid for us ... View more

Was this happening before the firmware upgrade ?  If not, try a roll back. If it was, is it happening on both 2.4ghz and 5ghz band on the same SSiD ?  Check the RF stats for utilisation, number of clients etc on the worst affected AP, has this increased in the last 30 days ? Any changes to DHCP scopes ?  Are these bridged or NAT clients (or both) ? Any potential new sources of interference ?  Check air marshall for spoofs, rogues ap's etc Check channel utilisation Any upgrades to the client devices, NIC updates etc ?   Good luck ... View more

Drop a ticket with support, they can, and do, apply whatever version of firmware you need to a network upon request.  I just got them to apply 24.12 to a test network where I'm having issues with later firmware and a particular vendor's nic/antenna ... View more

@Raj66  Thanks for checking this out further.   So, is it possible that for some models (i.e. MR32) after a firmware upgrade (i.e,. 26.6) that the dashboard is reporting the latest fimrware is installed (26.6), but in fact the firmware actually running on the AP is a lower version (26.x) ?   Or did I imagine that banner popping up on the dashboard (it's been a hard week lol) ?   cheers ... View more

@BrechtSchamp  wrote:   " It's possible. The MR32 is EOL, so it could be that there's a maximum software version it can run. "   End of support (EOST) for the MR32 is Jul 2024.  I would expect firmware releases, patches, new features etc to be made available for this and any other model up to the EOST date.  This article below suggests that this is the case   https://meraki.cisco.com/support/#policies:eol ... View more

No, the firmware version is reported as 26.6 after the upgrade of the MR32 (and MR16 network I tested), but the banner message (I wish I captured a screenshot) prior to the scheduled upgrade said something along the lines of ' a new version 26.6 is scheduled to be installed....only MR45/55 will actually be running 26.6, all other ap's will be running 26.3' (but will report in dashboard as running 26.6)   Perhaps a Meraki employee can give us the definitive answer on this? ... View more

Yes, it will report in dashboard under firmware as running 26.6 but from what I can tell from the banner message I saw earlier those ap's are actually running 26.3...only the mr45/55 models are running 26.6   We have had a previous experience of what we thought we were running a particular version of firmware (as reported in dashboard) but were in fact actually running an earlier version (MR32's) ... View more

Have just tested, looks like it reverts back to the original version that was on that network before upgrading to 26.6.  I'm still uncomfortable with particaular versions being applied to specifi models only and that if you think you are running a specific version of firmware (i.e. 26.6) but you are actually running a lower version, and there's no way of telling unless you know in advance...   ... View more

Goodbye and good luck Caroline !, and thanks for building the community from scratch.   Welcome back anytime you need a rest from the new day job !   Paul ... View more

I find the local status page (my.meraki.com) a handy tool for clients to check what connected AP, signal strength and throughput ('run speed test') if experiencing any issues.   If you, like me, find it handy, just make the local admin password something impossibly long and complex, you do this in one place, in the dashboard, Network-Wide>General ... View more