Yes,   I just updated the firmware on three of my Z3s yesterday and after reboot, they each took anywhere from 15 to 20 minutes before any traffic was routed down the WAN interface. (I probably should have documented it with some screenshots, but I just went about doing other tasks while waiting for them to come back).   So to clarify, upon reboot, within a few minutes they are detected by the Meraki dashboard, appliance status indicates an active wan connection, but if I initiate a ping to anything on the other side of the VPN, for 15 to 20 minutes I get 100% packet loss.   If I to to the Tools, I can ping the WAN appliance, run traceroute, MTR, DNS lookup, and ARP table all work fine, but I cannot ping anything on the other side or traceroute to the other side for 15 to 20 minutes.   If I navigate to the VPN status under the Monitor options it knows it is suppose to be looking for the MX68 peer, but the status dot is red and the connectivity indicator bar is red. Uplink decisions indicates that it is seeing the MX68, but no packets are flowing.   The three indicators: VPN Registry, NAT type and Encrypted are all green as well.   Hope that helps.   Very odd. ... View more

I'm having the same problem with our Z3 Teleworker devices. Sometimes they work themselves out of it, sometimes they reconnect with no issues. It's very frustrating. We have to fall back to having our users connect with the Cisco Secure Client, which defeats the whole purpose of deploying Z3's as a more secure method of connecting corporate equipment to our network. I am on the latest firmware as of this date. MX 18.211.2 Upon reboot, my Z3s also connect to the Meraki cloud just fine, they even show that they have established a VPN tunnel with the MX68 but VPN status is down, and no traffic will pass through the tunnel. ... View more