Meraki

CIreland · ‎Sep 18 2017

Hi, we had the same issue here. It turned out to be a problem with the timeouts and NAT-T. We ended up with phase 1 28800, phase 2 14400 and Meraki support disabled NAT-T (this was a configuration override that only support can do) for that endpoint it has been stable for us since.

CIreland · ‎Sep 18 2017

We have a MX84 cluster in a far flung site, we are changing the local ISP and therefore the WAN IP address. We use a virtual IP for non Meraki VPN termination. Can someone recommend the steps for changing the WAN IP? Would it be: Remove virtual up-link IP, change primary IP, change spare IP, add new virtual up-link IP?

Meraki

Community

About CIreland

CIreland

Community Record

Badges

Re: VPN stops passing traffic between Meraki Security Appliances and Cisco ...

MX84 Cluster change WAN1 IP

Re: VPN stops passing traffic between Meraki Security Appliances and Cisco ...