Can someone help me understand why the AutoVPN flaps like this? I have numerous sites that are doing this. Their internet connections are solid with no packet loss. In the past, I have emailed support and they have done something their end to correct the issue.
I'd prefer to prevent this from occurring than needing to managing it when it happens. What can I do to prevent this from happening?
this usually happens at the ISP side, e.g. Site A & B are using different ISP providers that set some policies for some traffic cross carriers.
So are you saying the AutoVPN only works when both sides are using the same ISP?
No. I was saying that crossing different ISPs would make the VPN connection unstable.
I have the same issue with my corpNetwork@home setup as the following.
You can see the tunnels for myself and my colleagues connecting to the office Hub were going up and down frequently.
But this is a general challenge, may not be your case.
One piece of advice is that you can add the peer IP as an uplink monitor destination on your MX, at least to see if there is packet loss.
Your logs showed the connection challenge with the Meraki VPN registry, not really the VPN tunnel between MXs.
therefore, it should not impact the actual traffic going through the VPN tunnel.
worse case, it may impact tunnel establishment for new VPN peers.
Thanks @Jim_Liang just to confirm, the message I am seeing doesn't mean that the VPN tunnel is dropping, it is more an "internal" message about the registry that is controlling the AutoVPN service. Am I correct in saying this?
That's correct.