site to site VPN registry (aka Meraki site to site VPN being unstable)
In the last few weeks we have had to open multiple support cases for different sites due to the fact that their Site to site VPN between MX appliances in the same organization was unstable. Support "changes the VPN registry" due to the "registry being overloaded" and this resolves the issue.
This is VERY frustrating to me on multiple points:
If the registries are overloaded then fix the real problem
This shouldn't require me to open support tickets to fix
There is no way that I can see what registry is being used, if it is the problem or not... I just open a ticket, and cross my fingers that support will fix it.