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.
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...
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...
Seen this one before — when switches show "configuration out of date" but the uplink otherwise looks fine, the first place I'd look is upstream firewall filtering. Basic internet can be working while the specific traffic the switch needs to reach the...
Thanks Noel — appreciate the scar tissue, that's exactly the kind of detail I was hoping to surface. The spoke-side route preference check before the cut lines up with what bit us early on, and staging the restore so AutoVPN registration settles befo...
Good question — we looked hard at that, and it doesn't fit our topology. The constraint is a hard dependency: every store is a spoke that has to reach two hubs, its in-country head office and the HQ DC concentrator. For the in-country stores to tunne...
