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 now- About ITSDigital
About ITSDigital
ITSDigital
Here to help
Member since Feb 15, 2023
Community Record
11
Posts
9
Kudos
0
Solutions
Badges
a week ago
Here's a redacted event log of a site which had it occur today: Time(GMT) Category Event type Details Nov 25, 2025 08:29 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:38485, connectivity: true" Nov 25, 2025 08:29 BGP BGP session established "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512" Nov 25, 2025 08:29 BGP BGP session established "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512" Nov 25, 2025 08:29 BGP BGP session established "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512" Nov 25, 2025 08:29 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:36415, connectivity: true" Nov 25, 2025 08:29 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:46946, connectivity: true" Nov 25, 2025 08:29 Route tracking Route connection change "peer_type: l3_vpn, peer: [REDACTED_MAC], connection_status: connected" Nov 25, 2025 08:29 Route tracking Route connection change "peer_type: l3_vpn, peer: [REDACTED_MAC], connection_status: connected" Nov 25, 2025 08:29 Route tracking Route connection change "peer_type: l3_vpn, peer: [REDACTED_MAC], connection_status: connected" Nov 25, 2025 08:29 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:36415, connectivity: true" Nov 25, 2025 08:29 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:46946, connectivity: true" Nov 25, 2025 08:29 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:38485, connectivity: true" Nov 25, 2025 08:29 Meraki VPN VPN tunnel "msg: FIPS mode disabled" Nov 25, 2025 08:28 BGP BGP session no longer established "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512, new_state: Close" Nov 25, 2025 08:28 BGP BGP sent notification "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512" Nov 25, 2025 02:00 Appliance status Primary uplink status change "uplink: 0" Nov 25, 2025 02:00 Meraki VPN VPN registry connectivity change "vpn_type: site-to-site, connectivity: true" Nov 25, 2025 02:00 Appliance status Primary uplink status change "uplink: 1" Nov 25, 2025 02:00 Meraki VPN VPN registry connectivity change "vpn_type: site-to-site, connectivity: false" Nov 25, 2025 01:59 BGP BGP session no longer established "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512, new_state: Close" Nov 25, 2025 01:59 BGP BGP sent notification "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512" Nov 25, 2025 01:59 Route tracking Route connection change "peer_type: l3_vpn, peer: [REDACTED_MAC], connection_status: disconnected" Nov 25, 2025 01:59 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:36415, connectivity: false" Nov 25, 2025 01:59 BGP BGP session no longer established "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512, new_state: Close" Nov 25, 2025 01:59 BGP BGP sent notification "peer_ip: [REDACTED_IP], local_as: 64512, remote_as: 64512" Nov 25, 2025 01:59 Route tracking Route connection change "peer_type: l3_vpn, peer: [REDACTED_MAC], connection_status: disconnected" Nov 25, 2025 01:59 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:46946, connectivity: false" Nov 25, 2025 01:59 Meraki VPN VPN tunnel connectivity change "vpn_type: site-to-site, peer_contact: [REDACTED_IP]:38485, connectivity: false"
... View more
a week ago
We have an intermittent AutoVPN issue with our multi hub-to-spoke organisation. Our hubs and spokes are all directly attached to DIA connections with public RIPE IPs with no upstream firewall. All hubs have fibre ethernet leased DIA connections. Spokes have a mixture of technologies: FTTC, FTTP and fibre ethernet. All spokes are connected to three hubs via full tunnel AutoVPN. The recurring issue: after a short period of packet loss on the WAN side of a spoke - some or all of the AutoVPN tunnels do not re-establish by themselves. Clients and the MX itself on the spoke networks can reach the internet when the tunnels drop, the Meraki VPN registry stays contactable, but the tunnels do not always rebuild automatically. This requires us to manually change the spoke's Site-to-Site VPN configuration to Off, save config, then set back to Spoke again before the tunnels will rebuild. We see the issue occur when: * Most common: the spoke MX WAN has an upstream NAT router (no firewall rules, NAT type friendly). * Least common: the spoke MX WAN has an upstream Draytek 167 VDSL modem (PPPOE mode, no firewall, no NAT). The frequency of the issue is every week when in NAT mode. Around a month or so in PPPOE modem mode. We are using firmware MX 19.2.4 but have seen the issue on the 18.x release train. Meraki support has been engaged with multiple times but have not been able to confirm a root cause, but were leaning towards it being a ISP issue. This issue has occurred on multiple ISPs, nothing is configured on the WAN/ISP side to inhibit NAT or VPNs. No carrier NAT or WAN firewalls. The issue also occurs if only one hub is connected via AutoVPN. Has anyone else seen this kind of issue occur?
... View more
Labels:
- Labels:
-
Auto VPN
Oct 16 2025
12:40 PM
Will do this, quite tricky to pull logs due to customers rebooting switch to restore service. But they may have another approach to diagnostics.
... View more
Oct 13 2025
1:27 AM
Over the course of the last year, since we started deploying MS130 switches into 40+ sites, we periodically find them dropping TCP traffic and losing manageability. The MX stays online, and any other MS120 switches are that are directly uplinked to the MX. Our environment is fairly simple: MX with dual WANs connected to INET MX downlinked to MS (1 or more). MS connected to APs and Windows PCs. Any ideas on what could cause this type of issue, or would it be a hardware RMA issue? The issue only occurs intermittently. Firmware in use: MS 17.2.1 Also the incident which occurred today had this in the portal:
... View more
Labels:
- Labels:
-
Layer 2
Aug 21 2025
1:49 AM
We run tens of them, and no lockups. Our 75's are running newer firmware (19.1/19.2), but never saw it on the older 18.x train.
... View more
Dec 20 2024
8:49 AM
2 Kudos
NONAT has to be turned on first in Organization > Early Access. Docs are here: https://documentation.meraki.com/MX/Networks_and_Routing/NAT_Exceptions-No_NAT_on_MX_Security_Appliances And I was wrong, BGP route exchange is available on NONAT routed mode - but only on firmware 18.207 or above: https://documentation.meraki.com/MX/Networks_and_Routing/Border_Gateway_Protocol_(BGP)
... View more
Dec 19 2024
4:43 AM
You could deploy in routed mode, if you enable NONAT on the WAN interface connected to your MPLS. You'll be able to route in and out of the MPLS and apply L3 firewall rules to the traffic flow. This is only If you dont mind enabling opt-in "beta" functionality, which NONAT is labelled as. But we've been successfully using it in production as a stop gap until we move everything behind Meraki AutoVPN and NAT. You'll also not get BGP route exchange, and the MPLS will be treated as an external network, so advertising status routes from the hub might be required depending on your topology and needs.
... View more
Oct 9 2024
4:40 AM
5 Kudos
I think the auto-reboot function would be great providing: * You can turn the functionality off in the dashboard with a tickbox per network. * The reboot reason and crash data is uploaded to the cloud once connectivity is restored.
... View more
Sep 5 2024
3:53 AM
2 Kudos
Source NAT would be a super handy feature we could use. Hopefully it's still on the dev todo list.
... View more
Sep 2 2024
5:30 AM
On Saturday, during the early hours , we had two MS130-48 in different Orgs with 16.8 and 16.9 firmware both stop forwarding DNS but still allowing TCP/ICMP packets to pass. Looking into 17.1.2 as a fix.
... View more
My Top Kudoed Posts
© 2025 Cisco Systems, Inc.
