Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Become a member of the Cisco Meraki Community today
Get answers from our community of experts in record time.
Join nowAbout IFST
IFST
New here
Member since Jun 29, 2025
Wednesday
Community Record
4
Posts
0
Kudos
0
Solutions
a week ago
Yes, you are right. I was able to establish VPN connectivity with three sites using the old routers. Let me put them into production and see how it goes. Moving forward, I will place Meraki at the sites to replace the old ones.Thankyou all for the insights and support .I will post accordingly.
... View more
a week ago
Hi, I have DDNS set up at our headquarters, but when the Meraki device is replaced, it generates its own dynamic name. I’m wondering if I really need to configure DDNS for the site in Meraki and then input the hostname into the Cisco 800 router. Additionally, I would have to add the DynDNS link in the Cisco router using the IP DDNS update method via HTTP so that Meraki can recognize the site peer. This seems like double entry, and I'm concerned because the DDNS in the Cisco router is unreliable; it doesn't resolve the public name immediately, and sometimes we need to manually add the public IP on dyndns.org. It's becoming a headache. In contrast, Cisco to ASA or other Cisco setups didn't have these issues. I thought Meraki would be easier to manage.
... View more
a week ago
The Meraki side has its own dynamic name, but on the remote side Cisco 800, we don't have a dynamic name since it is a spoke connecting to the Meraki hub. Does this require DDNS on the remote side?
... View more
a week ago
Dear Team, I have a new Meraki MX 105 and I'm looking to establish a site-to-site VPN over IPsec with a Cisco 800 series router using IKEv1, while replacing an ASA firewall. Currently, the ASA firewall and 21 sites utilize Cisco ISR routers from the 800 and 900 series, and everything is functioning well. The Meraki MX 105 is located at the head office and uses a DDNS service (dyndns.org), while the remote sites also have dynamic IP addresses from their ISPs. Both peer connections work well with the ASA and Cisco ISR routers, but when I switched to the MX, the sites fail to connect. The error message displayed is MM_NO_STATE. If anyone has resolved a similar issue or has a sample configuration for a non-Meraki peer using dynamic IP addresses, please share it. Thank you!
... View more
Labels:
- Labels:
-
Other
© 2025 Cisco Systems, Inc.
