@KarstenI thank you for your feedback, it's appreciated.  Hoping others reply as to how their limits are set for comparison - similar to your 1% or if different (and maybe why)..  Thank you again. ... View more

@MRCUR Tech Support sent me these instructions that fixed the issue for my particular setup (7/26/24) and it DID fix the issue: Thank you for contacting Meraki Technical Support! Can you temporarily enable the WAN3 Backup feature, modify the WAN 1 bandwidth settings, and then disable the WAN 3 backup feature, and then try modifying the WAN 1 configuration again just to ensure the WAN 3 backup feature is no longer being referenced? Keep in mind, when temporarily enabling the WAN 3 backup feature, the physical port usage will change to the following: On the MX85, MX95 & MX105 - The Fourth physical port is the designated backup port. Physical ports 1 & 2 become designated WAN 1 and WAN 2 ports.   I am glad to have it resolved and apologize for not posting this sooner - my struggles are real. ... View more

Thanks for sharing the feedback, it's appreciated @lcoalson  ... View more

And I am getting good WAN results everyday yet one day all SSIDs are limited at 100Mbps?   ... View more

Yes - indeed hilarious.  Not buying that logic or explanation either.  This setting is at 100Mbps for every AP in 4 organizations and 11 networks, two of those locations have 2Gig (down) / 1Gig (up) WAN bandwidth.  Neither of those 2 locations are capped at 100Mbps.  This is definitely GUI'd for sure. ... View more

@lcoalson  have you gotten any response on your support ticket?  If so, was there any explanation?  Asking because all of my MRs (production) have 100mb per-SSID bandwidth limit.  I have had to "manually" put in higher numbers so as to not be limited. ... View more

And I also checked MR36 uplink and it shows 1Gig to eliminate wiring or uplink speed negotiation. ... View more

Correction: I moved a MR36 from one organization to another MX75 and when I opt to configure SSID1 or SSID2 it lists 100 Mbps however SSID3 and higher show unlimited. Not sure why it wouldn't allow me to edit initial entry. ... View more

@lcoalson - I moved a MR36 from one organization to another MX75 and when I opt to configure SSID1 or SSID2 it lists 100 Mbps however SSID1 and higher show unlimited.  I am not able to make SSID1 or 2 go beyond the 100 Mpbs limitation.   MX75 on MX18.211.2 MR36 on MR30.7 I concur with being limited to 100 Mbps on SSIDs 1-2 even when attempting to configure Per-SSID bandwidth limit.  I will try to configure SSID3 instead to see if it's default listing of Unlimited remains in tact once configured.     ... View more

@FamousDave what firmware are you running? ... View more

@BlakeRichardson - I (too) took a MX105 offline at 7:53PM CDT and got notifications at 10:22PM CDT.  So I concur with your discovery of delayed SMS alerts. ... View more

If wireless device has private relay or some type of app VPN, be sure it's OFF to get direct results. ... View more

I just found it in the documentation: The dashboard periodically polls for SFP telemetry every 5 minutes. And the module updated as well - appears the SFP+ module #1 was bad as #2 is getting good specs/readings. ... View more

Thank you @PhilipDAth  ... View more

Important notes This version's IOS image is based on 17.12.3 CCO. Upgrades to this version will result in a full system reload. New feature highlights Client Analytics Device Uptime EEE (Energy Efficient Ethernet) Support (API Only) Multi-auth with support for guest/failed/critical RADIUS Caching VLAN to SGT mapping Fixed issues Fixed an issue that caused the Switch Port Packet Counter Live Tool to incorrectly underreport packet counts Resolved an issue where multiple MS390s sharing a VLAN and data link could produce a multicast flood due to mismatched IGMP query interval and timeout settings General known issues Meraki native switches move LACP ports to an active forwarding state if configured. This can cause loops when connecting to an MS390 or other Catalyst switch unless the bundles are configured on the Catalyst side first. All Meraki native ports are configured in passive LACP mode so that loops do not occur between Meraki native switches (always present) Ms390 known issues MS390 stacks may fail to apply new configurations fetched from the network. This results from an issue with the NETCONF application, leading the system to revert to the previously stored configuration. MS390s in stack configurations may experience high memory consumption, which can result in authentication failures. Reloading the active switch temporarily resolves the issue. Packets between clients on separate VLANs may be stripped of their SGT when routed through an MS390 Stacks of 5 or more MS390s may experience a configuration mismatch when making multiple consecutive port configuration changes to several interfaces in a row ... View more

Sorry - I should have included that this site serves as a HUB for 4 remote sites with 5 VLANs per site.  Each remote site has 1 VLAN enabled for VPN access to the HUB.  I felt configuring L3 routing at the HUB to be the best option or choice for the setup. ... View more

framework for future features....say it twice🤣 ... View more