Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Lessons from splitting a 1,200-site Meraki organization into threeWe run a retail network of ~1,200 stores and warehouses across 62 countries, all on Meraki. Everything sat in a single org, and the AutoVPN route table had grown to the point where it ...
Sharing a scaling problem we recently worked through, and opening it up for discussion — I suspect other large multi-region customers hit the same wall.The problemOur environment is a multi-region AutoVPN deployment that grew organically into a large...
Thanks for posting the numbers, that comparison says it all.Same hub count as us, several times our subnet density, and a fraction of the route count. H2H really was the only variable.On Network Move, standalone-only would explain a lot. Our whole es...
Happy to explain the shape of it.We have 50+ hubs, roughly one per country. Every spoke builds two tunnels, one to its in-country hub and one to the HQ concentrator, because a large share of traffic terminates centrally. On top of that, every hub als...
Thanks for the interest, glad the writeup was useful.The tool is entirely mine, not my employer's, so I'm free to share it. It needs a bit of shaping per environment, every org is different, so I'd rather set it up with people than just hand over a z...
I am experiencing the issue described in the fix below on devices such as the MX64(W), MX65(W), MX84, MX100, and vMX100. Since these devices can only be upgraded to a maximum of firmware version 18.107.13, does anyone have any idea what the solution ...
You're right that the capability exists — Meraki Support confirmed they can do this. The catch for us was scale: we've been working it with them for 3-4 months, and I think our org is just large enough that the move hasn't been able to move forward o...
