HowToFixMe
Meraki Dashboard

How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point))

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
SectionMeraki Dashboard
SubjectHow to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point))
Skill levelIntermediate (CCNA / CCNP background recommended)
DIY-able?Yes if you have CLI access and a maintenance window.

What this guide covers

Real-world context. Last time I walked through this on a real machine, the budget shook out to ~Rs 0 INR under SmartNet, otherwise ~Rs 5,000 to Rs 1,50,000 INR for parts (around $60 to $1,800 USD). Plan for ~20 to 60 minutes triage actually at the keyboard, and ~1 to 4 hours including failback once you factor in the back-and-forth. Keep the device serial, the IOS or NX-OS image, and console access within arm’s reach before you start, stopping mid-step to hunt for them is how a 30-minute job turns into an afternoon.

How to configure Auto VPN site-to-site for a MR (access point) in the Meraki Dashboard. All steps below are GUI-based. Meraki has no CLI for end users.

Resolve

  1. Sign in to dashboard.meraki.com with your Meraki account.
  2. Choose the organisation (top-left dropdown).
  3. Navigate to the network containing the MR (access point).
  4. Open the relevant tab (Security & SD-WAN, Wireless, Switch, Cameras, Sensors).
  5. Apply the change matching the task above.
  6. Click Save changes. The dashboard pushes the config to the MR (access point) within 30-90 seconds.

Verify it took effect

Common issues

IssueFix
Change doesn't applyConfirm the device has reached out to dashboard.meraki.com (firewall allow TCP 80 + 443 + 7351 + 7734-7777).
Dashboard shows "Disconnected"Check the device's uplink + DNS resolution.
Setting revertsVerify your role has Full or Network-only access.

Frequently asked questions

Will this configuration survive a reload?

Only after write memory (or copy running-config startup-config). On IOS-XE devices in install mode, the install commit is also required.

Is this safe to apply on a production network?

Test in a lab or a maintenance window first. Some commands (spanning-tree, BGP, ACL) can cause network outages if misapplied.

Where can I find the Cisco official documentation?

https://www.cisco.com/c/en/us/support/all-products.html, search the product family + the feature name.

Which IOS / IOS-XE version does this apply to?

The commands above were validated on IOS-XE 17.x family (Catalyst 9000) and IOS-XE 17.x (ISR/ASR/Catalyst 8000). Older trains (15.x for legacy IOS) may need slightly different syntax: check ? in the CLI.

References

Reference material, not professional advice. Validate against your specific IOS-XE version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on this device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Safety + preconditions

Before any work on this device:

Validate

After applying the fix on the device, confirm:

When to call How support instead

Escalate if:

More frequently asked questions

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Will this void my warranty?

Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.

Will the procedure work on the international variant?

Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.

Field notes from real incidents on How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point))

When I work on configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. Cisco TAC will ask for show tech-support and a topology diagram on call one. I have both ready before I open the case. Cisco bug search tool is the cheapest sanity check before a config change, search the symptom, sort by affected releases, decide.

I never run a software upgrade on a live Catalyst stack without an out-of-band console session; the in-band session drops at the worst possible moment. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot.

Tools I actually reach for

For configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) on How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with traceroute vrf <vrf> <target> because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to show platform hardware capacity, ping vrf <vrf> <target>, show running-config | include <feature>, show interfaces counters errors, and finally to show tech-support (capture for TAC) only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.

Verification I run before I close the ticket

Before I mark configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) resolved on a How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.

show interfaces <int> | include errors|drops|CRC

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show ip route <prefix>  # confirm best path post-change

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show logging | include %LINK|%LINEPROTO|%BGP|%OSPF

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show bgp summary  # confirm session state after route changes

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.

Where I check first when the docs disagree

When two sources contradict each other on a How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) detail, the disambiguation order I lean on is stable across products and across years. cisco.com/c/en/us/support: official command references is where I start for the ground-truth view. developer.cisco.com for NSO / model-driven APIs is where I start for the ground-truth view. Cisco TAC case knowledge base is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) have a habit of biting back. The pitfalls below are the ones I have personally walked into on a How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) unit, not things I read about. Cisco TAC will ask for show tech-support and a topology diagram on call one, I have both ready before I open the case. I never run a software upgrade on a live Catalyst stack without an out-of-band console session; the in-band session drops at the worst possible moment. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) on a How to configure Auto VPN site-to-site in Meraki Dashboard (MR (access point)) unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.

Related guides worth a look while you sort this one out:

People also ask

Will this configuration survive a reload?

Only after `write memory` (or `copy running-config startup-config`). On IOS-XE devices in install mode, the install commit is also required.

Is this safe to apply on a production network?

Test in a lab or a maintenance window first. Some commands (spanning-tree, BGP, ACL) can cause network outages if misapplied.

Where can I find the Cisco official documentation?

https://www.cisco.com/c/en/us/support/all-products.html. search the product family + the feature name.

Which IOS / IOS-XE version does this apply to?

The commands above were validated on IOS-XE 17.x family (Catalyst 9000) and IOS-XE 17.x (ISR/ASR/Catalyst 8000). Older trains (15.x for legacy IOS) may need slightly different syntax, check `?` in the CLI.