You will likely need to work with your Meraki partner and/or support. ... View more

Organizations using active legacy licensing models, such as Co-term or PDL, are unable to claim subscription license keys. Mixed licensing modes are not permitted​​​​​​.   Subscription - Licensing Claim Cloud    Subscription License keys can only be claimed by an expired organization, an organization in a grace period, or a newly created organization (this includes ones created via Organization split).  ... View more

What firmware are you currently running? Initial thoughts: this doesn't sound like a community fixable issue however you might consider opening a support ticket with engineering. Ways to Contact Meraki Support  ... View more

  Meraki Support  ... View more

Normally an indication of a client being further away from the AP.  Dense building materials could factor into that equation a bit too. ... View more

Perhaps so (kinda expensive) but it is an outdoor option. ... View more

Cisco Wireless CW9179F Access Point  ... View more

Are you an organization admin?   You can also customize this setting Organization > Configure > Settings by adding your e-mail address for licensing, hardware defects, and maintenance. ... View more

The WAN breakout switch should be in it's OWN (separate) network - not part of your downstream switches. ... View more

Give your feedback (previously Make a Wish)  ... View more

Give your feedback (previously Make a Wish)  ... View more

There is no method to delete Meraki AP connection logs or timeline logs from the Wireless > Overview section in the Meraki Dashboard. These logs are retained for network monitoring, troubleshooting, and historical analysis, and the Dashboard does not provide an option for administrators to manually clear or delete them. You can filter and view up to a month's worth of connection history, but deletion is not possible. ... View more

I'm not aware of any backend tweaks.  If this hub doesn't truly need to be full mesh hub, you could consider the idea of converting it to a spoke to reduce tunnel count and traffic.....or keep it as a hub and disable the multi-uplink with WAN2 tunnels only in a failover scenario. ... View more

Too bad the documentation couldn't outright lay it out explicitly.   I opened a support ticket a year+ ago just to make sure my single MX95 edge and MX95 VPN concentrator (both) were set correctly for client tracking.   Glad to say support assists when it's needed but would be ideal if the examples laid it out clearly. Just my 2¢. ... View more

And the winner is……   Cisco is not responsible for any network interruptions or outages caused by using trial equipment in a production environment. 😊 ... View more

Meraki Go Portal Alternatively, you can also open a case from your Meraki Go portal, by selecting Contact Support from the user icon dropdown in the top right (or by clicking this link). Meraki Go - Support or you can try emailing help@meraki-go.com, though submitting a case via the dashboard/app is usually preferred for quicker resolution as it links your network info.  ... View more

If this were my project, I'd be inclined to have the both MX250s in HA and MS350 stack in one combined network.     If the MS350 stack is using L3, you'd use unique identifier.   If you keep it at L2 then use MAC address — Default. Separately, I'd put the other MX250s (pair) in their own separate networks as an example MX250-VPN-A (it's own network - same organization) MX250-VPN-B (it's own network - same organization) You would then use "Track clients by IP address" for client tracking, and its deployment mode is "passthrough" (VPN concentrator mode).  This is the correct client tracking option for a standalone MX in VPN concentrator mode, as tracking by IP address is recommended when the MX is not the layer 3 gateway for clients.   Client-Tracking Options  ... View more

Thanks for sharing the video (had not seen it before) but have seen BRKEWN-2046 slide deck before.   Good stuff. ... View more

I've seen the ability to "clone an existing network" (not organization) which still doesn't protect one if the organization is deleted. ... View more

I'll be sure to check back on this post to see if you are able to find a solution outside of the PCI compliance, if one exists. Best of luck and cheers! ... View more

A close alternative: Meraki is certified as a PCI DSS Level 1 Service Provider (the most rigorous audit level). You can learn more about Meraki's own PCI DSS compliance at https://meraki.cisco.com/trust#pci  PCI Compliance with Meraki  ... View more

If interested, you can use the search box at the top of the page to see previous posts and responses about the need for backing up dashboard configurations.   ... View more

Cisco Networking App Marketplace might offer you 3rd party solutions but normally it's not necessary to do any backup configs. ... View more

I would safely say YES based on this: Note: The SM parts of a network may be automatically removed/deleted after the EOST date. Other parts of the network (e.g. MX/MS/MR/MV etc. will not be impacted). After the EOST Meraki SM enrolled endpoints will retain their last configurations from Meraki Systems Manager and be unable to communicate with the Meraki Dashboard to make any further changes.   Meraki Systems Manager EOL Migration  ... View more

On the Meraki Free Trials Change it states: Cisco is not be responsible for any network interruptions or outages caused by using trial equipment in a production environment." Could be changed to: Cisco is not responsible for any network interruptions or outages caused by using trial equipment in a production environment." or  Cisco will not be responsible for any network interruptions or outages caused by using trial equipment in a production environment." ... View more