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

Cisco Technical Influencer Hub (mid page) ... View more

Cisco Insider Champion 2025 Application is now open! (dated 12/9/24)  If you have any questions, please reach out to ciscochampions-pmo@cisco.com ... View more

I think you posted a question and @alemabrahao provided a response - then you changed your Q. Conversion from CLI-managed IOS XE Catalyst Switches to Cloud Management with Cloud Configuration  ... View more

Many thanks to all that participate!   Congratulations to all contributors.    👏 👏 👏  ... View more

The dashboard AI Assistant indicates:   Customers usually receive a single Meraki license key per purchase order. When this key is claimed in the Meraki Dashboard, it is split into individual codes for each device or license type, which is why multiple codes may appear after claiming. Hardware inventory codes and software license codes differ because hardware and licenses are managed separately in the Dashboard. If multiple codes are received for a single purchase order before claiming, it may be due to how the order was processed or bundled by the distributor or backend. After claiming, the Dashboard always splits the main license key into individual codes for assignment. Partners can be included as authorized receivers if their contact information is added during the order process by the account manager or distributor. For more details, see: Meraki Per-Device Licensing Overview Meraki Hardware and Software Onboarding Guide Meraki Per-Device Licensing - Configuration ... View more

Thanks @enovak for sharing the BRKOPS-1156 slides.  Yes, I have seen the other references shared.  Still consuming and digesting the materials.  Thanks again! ... View more

Optimizing Meraki-Managed Uplink Connections  is a free learning hub tutorial that might be of interest to you.  You can simply take it using the same credentials you use to log into the Meraki Community.   Thanks! ... View more

To split an aggregated link, simply select the aggregated port and choose Split. This will revert the changes and split the group into its own separate ports.   ... View more

If another admin has access, they can UNLOCK your account from the Meraki Dashboard - not likely from the mobile app. If that doesn't work, then they can re-create your account being an alternate option. I believe you'd have to turn off organization wide 2FA just for one person's account. ... View more

Two-Factor Authentication has a section that might be of interest to you: Recovering Access to Accounts Protected by Two-Factor Authentication   ... View more

another Meraki Dashboard admin from the same organization can reset your 2FA. ... View more

Do you happen to have the backup codes?  When you get the 2FA prompt, look for an option such as “Use a different authentication method” or “Send SMS code”. If that doesn't work, another Meraki Dashboard admin from the same organization can reset your 2FA. Contact Cisco Meraki Support: If you have no other way to access the dashboard, you can submit a support case through this form. Note: Dashboard organizations should always have at least two organization admins with full permissions. This is best practice in case one account is locked out or if access to that account's email address is lost. Managing Dashboard Administrators and Permissions  ... View more

There is generally no advantage to manually specifying Umbrella DNS servers on the MX WAN uplink when you have already integrated Umbrella via API and are applying policies at the MX/MR level. With API integration, Meraki devices use their identity to enforce Umbrella policies, and DNS traffic is automatically routed and protected according to those policies.   Manual DNS configuration is only necessary for non-Cisco devices or networks that cannot use API integration. For Meraki MX/MR with API integration, manual DNS configuration does not provide additional security or policy enforcement benefits, and the integration is designed to prevent users from bypassing Umbrella by changing their DNS settings locally. ... View more

Zscaler Internet Access (ZIA) Integration  ... View more