I would be interested to know how your RMA swap goes, @Stephen_P . Meraki support had suggested that for us at one point, but we resisted because our issues were present regardless of which member of our HA pair was acting as the primary unit.   We haven't run into the MX device reboot issue, though the issues that have been plaguing us for almost the past year seem just as bad sometimes. We have been seeing random drops of our WAN connections at seemingly random times during the day (all WAN traffic stops for 1-3 minutes). We've also been fighting a problem where the MX stops passing certain traffic, and we have to modify a firewall rule (any firewall rule) to get it to start passing traffic again. At least for that issue, I can proactively "poke the firewall" each morning, and that seems to keep that issue at bay for the most part. I haven't found a way to prevent the WAN drops, which can be nearly as challenging as a device reboot, but "thankfully" only happen a few times a week. ... View more

Major update to my issue (fingers crossed).  My Meraki MX250 setup is still not in production, as I really can't move it there until I get this particular issue with 1:1 NATs fixed.  I was starting to think the issue was based on 1:1 NAT problems.  A Meraki engineer found that my internal server was not showing up on the ARP table (this was a day after the last test hour I used to fix this.)  And, stated that a 1:1 NAT won't even try to work unless the destination is in the ARP table.  I'm wondering if there is a length of time needed for some machines to properly be entered into the ARP table on the Meraki?  I usually only have about 1 hour of time for testing production equipment (i.e. allowed down time) and within that time my testing of the final production destination machine never answered calls.  However, I put a simple IOT device into the test environment that the Meraki is currently in, and it also failed 1:1 NAT setup calls to port 80 and 443 initially.  But, I left it there and after 24 hours I tried again and it worked.  I can't say the amount of happiness of this discovery is overcoming the frustration in getting to this point is a positive for me yet.  But, hopefully I can find a way to setup my Meraki into production with the final destination in place and working.  I just don't know 1. why the machine didn't show in the ARP table within the 1 hour, and 2. how long should it take? ... View more

Hi All,  Thank you everyone for taking your time to respond on my query. This has been fixed, and it was identified that there were few clients in LAN which was keep sending IPv6 request to MX. The MX02 got overwhelmed due to this and unable to see VRRP from MX01, and assumes the MX01 isn't available and it started becoming master. After few seconds, it receives VRRP from MX01 and then it becomes standby. The event log doesn't show any IPv6 DHCP logs and Meraki TAC informed us that it is visible only in backend, and they suggested to block IPv6 in Switch ACL until we remove IPv6 on those clients. ... View more