AutoVPN Connectivity Issues

sttaylo2
Meraki Employee

We are aware of an ongoing issue with AutoVPN Connectivity.

 

This is being treated as a Severity 1 issue and the appropriate resources have been engaged.

 

We will provide updates in this thread as they become available

4 Comments
sttaylo2
Meraki Employee

We have identified the issue to be related to redundant routes for AutoVPN.

 

An identified workaround is to stop advertising routes from secondary hubs temporarily

 

sttaylo2
Meraki Employee

This issue has now been resolved by our engineering teams.

 

We recommend making a change on any affected networks, such as adding or removing a spoke to trigger devices to fetch an up to date config.

GiacomoS
Meraki Employee

Good day Community,

 

Please be aware that we are continuing to work on this, as devices are not automatically receiving the up to date configuration.

 

A manual change is required at this time to quickly force the affected MXs to download the correct configuration; example actions that can be taken to trigger a configuration request:

- Adding or removing VPN spokes

- Temporarily adding a new VLAN

- Temporarily changing one of the uplink DNS servers

- Changing either the trunking mode or allowed VLANs on unused ports

 

Please do get in touch with Support if the issue persists after attempting one of these changes.

 

Many thanks!

Giac

GiacomoS
Meraki Employee

Hi all,

 

Final update here that this is now resolved. 

 

All devices should eventually fetch the new configuration and have the problem resolved, although this may take up to an hour. 

If you are impacted by this at the moment and need urgent resolution, please attempt one of the above changes. 

 

Should you still see unexpected behaviours, please don't hesitate to get in touch.

 

Many thanks!

Giac