Skip to content

Incident detail

Issues with Auto VPN

Resolved incidentMajor

Timeline window

to

Get alerted the next time Cisco Meraki breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are aware that some customers are experiencing Meraki Auto VPN issues, and we are actively investigating. Rebooting MX/vMX devices operating in passthrough mode can be used as a workaround in the meantime.

  2. Identified

    We have identified a proximate cause for the Meraki Auto VPN issues and are working on a remediation plan to restore normal service. A fix will be deployed to that effect shortly.

  3. Investigating

    We continue to investigate the root cause of Meraki Auto VPN connectivity issues in MX and vMX appliances running in passthrough mode and are working to remediate them.

    Customers can restore service by rebooting the appliance in Passthrough Mode via the Meraki dashboard.

    For steps to reboot your device please follow the below knowledge base article:

    https://documentation.meraki.com/MX/Monitoring_and_Reporting/Using_the_MX_Live_tools#Reboot_Appliance

  4. Identified

    Meraki engineering identified an issue with MX and vMX devices operating in Passthrough or VPN Concentrator mode and are working to test and deploy a fix. In the meantime, customers can reboot MX and vMX devices operating in those modes to restore service.

    For steps to reboot your device please follow the below knowledge base article:

    https://documentation.meraki.com/MX/Monitoring_and_Reporting/Using_the_MX_Live_tools#Reboot_Appliance

  5. Identified

    Customers potentially affected can restore service by rebooting MX and vMX appliances operating in Passthrough or VPN Concentrator mode.

    Meraki Engineering has tested a fix and are in the process of deploying it. Once deployed, we anticipate that MX and vMX appliances that have not already been rebooted will experience up to two minutes of disruption to the following services: AnyConnect, eBGP, Connection Monitoring, and IPSEC VPN Tunnels.

    For steps to reboot your device please follow the below knowledge base article:

    https://documentation.meraki.com/MX/Monitoring_and_Reporting/Using_the_MX_Live_tools#Reboot_Appliance

  6. Monitoring

    Meraki Engineering has begun to deploy the fix to this issue. It is expected to be complete by approximately 18:30 UTC. Once deployed, we anticipate that MX and vMX appliances that have not already been rebooted will experience up to two minutes of disruption to the following services: AnyConnect, eBGP, Connection Monitoring, and IPSEC VPN Tunnels.

  7. Resolved

    This incident is now resolved. If you are still experiencing any issues, please contact Meraki Customer Support.

Keep exploring

More from Cisco Meraki

Neighboring incidents on Cisco Meraki's timeline and the rest of their record on OutageDeck.