AutoVPN issues with WAN 2

P4ck3ts
Here to help

AutoVPN issues with WAN 2

hi,

 

WAN 1 is set to primary uplink with load balancing disabled. AutoVPN works fine.

 

When I add WAN 2 into the mix, RDP connections go down. Active-Active AutoVPN is set to disabled by the way. But the issue still persists.

 

any help appreciated. 

thanks

5 Replies 5
RaphaelL
Kind of a big deal
Kind of a big deal

What MX model  ?

What MX version ?

P4ck3ts
Here to help

mx100 running 18.107.

 

to add WAN 2 is under NAT.

cmr
Kind of a big deal
Kind of a big deal

Is it 18.107.4, or the unpatched version

If you try the NATed connection on its own what do you get?

If my answer solves your problem please click Accept as Solution so others can benefit from it.
P4ck3ts
Here to help

i will try on a non workday as I can't have this site down. I think both WANs need to be connected to the VPN registry. WAN 2 is under CGNAT and I think its blocking the UDP hole punch 

LindseyG
New here

There's a known issue with MX's on v18.107 that in certain scenarios when you have a HA pair, if you make changes, it causes services to restart, including VPN's.

 

There is an internal case at Meraki and my case is linked to it.

 

The details i got told were:

 

Certain changes have been seen to cause services to restart, causing VPN tunnels to drop and reform when running an HA pair of MX’s on firmware version 18+:

 

  • Firewall rules changes
  • DHCP scope changes
  • Layer3 changes to VPN-enabled subnets/routes
  • Bringing up disconnected WAN2/Cellular interfaces from the “disconnected” status
  • Enabling or disabling content filtering

I'd raise this with Meraki so it gets linked to their internal case.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels