FWIW in my lab here I often see flapping if I also point to 2 concentrators. I think it aligns to an open bug. Not sure if your Support case is already linked to that bug. Support would need to confirm. To facilitate concentrator redundancy you might need to do a MX HA pair (2 MXs) at just DC1 as that may not encounter the same flapping as specifying a primary and secondary concentrator under the SSID. It would just point to one MX network that is a HA pair. Looking at your diagram that would also likely require some changes if what happened was the inside interface of the DC1 FW was down. So, either connecting the MX HA pair directly to FW LAN ports if possible or using LAG/LACP between the FW and Core. Again, all general assumptions as not knowing what those actual pieces of hardware are capable of supporting. I understand this wouldn't help if the failure is total DC1 outage. I'd involve your Meraki SE for a design discussion though if that's not already occurred. Bottom line the design as you have it might not be feasible at the moment if the tunnel flapping is a bug (which I believe it is, again Support would need to confirm). Just trying to provide a little more context while you work on this with Support. Also, yes the "new version" UI for the reassociate clients feature is busted. You have to toggle into "old version" to enable/disable it. I think this has maybe been busted for a long time (ever since new version was implemented). As for the DHCP probe piece. I don't know for sure. I would also need to check out pcaps and see if it can be determined.
... View more
