As per title.
Meraki instructions have no references to High availability, redundancy or anything of that sort :/
There's no point running a traditional HA cluster as you need the second unit to be standalone in its own subnet and separate AZ for obvious reasons.
I was thinking run it as a lower priority hub then use a lambda to rewrite VPC route tables if the primary EC2 instance goes down?
As someone that has been writing a "Why I hate Meraki" book for the last 3 years (kinda joking) I have found that any kind of redundant design can be hampered by using Meraki unless you use their products in a very specific configuration.
I agree there is little documentation on HA/redundancy for Meraki, however there is this one if you haven't already been through it:
https://documentation.meraki.com/MX/Deployment_Guides/Datacenter_Redundancy_(DC-DC_Failover)_Deployment_Guide
Meraki is the small business wireless solution that enterprises want to scale up to company-wide deployments, but are then frustrated when they find out that it's still a small business solution in terms of what it offers.
Its basically as I thought, use AWS duct tape to write scripts to re-point subnet route tables, or make sure your entire infra is AZ independent.
Couldn't even get any reference doc, the SE had to write it out by hand lol. This is unlike every other vendor who have reference multi-AZ HA deployment topologies (and usually cloudformation and lambda scripts ready to roll).
Its great for what it is, pretty graphs mm mmmm mmmm. Gotta find out who's burning all that youtube bandwidth. 802.1x integration and identity based FW or URL filtering is a piece of cake, that's a massive tick.
Quote from: wintermute000 on March 22, 2019, 03:28:21 AM
Its great for what it is, pretty graphs mm mmmm mmmm. Gotta find out who's burning all that youtube bandwidth. 802.1x integration and identity based FW or URL filtering is a piece of cake, that's a massive tick.
^ TRUTH
Anything that makes 802.1X easy to use is gonna move product.