Has Meraki produced documentation for this yet?  We just turned on a number of alerts for our network and are tweaking them to see what works for us.  I read this thread earlier and we decided to get weekly alerts.  For this week we have 3 alerts at 3 different offices.  One is here at our HQ and I was able to find who it is and verify there was no issue.  But the other two are clear across the country, and one of them is on wifi so I can't cycle the port as suggested above.  How do we troubleshoot these alerts to determine whether it's a false positive or a legit concern, without physically going to the device and looking for vmware (which shouldn't be on it based on group policies anyway)? ... View more

@ospsms, start with checking the status of the AutoVPN, make sure it is actually up. And check the route table to make sure the subnets of the other site have been learnt by the MX. ... View more

The local page indicated DNS problem... Since I moved the MX68 to the edge of the network before ISP Cloud based Firewall... The key Meraki FW policy to reach 8.8.8.8 Uplink connection monitor was the key to sustaining communication with the Meraki Cloud.   Source IP     Destination IP   FQDN   Ports   Protocol   Direction   Description   Devices using this rule       5 total Your network(s) 108.161.147.0/24, 216.157.142.0/24, 216.157.143.0/24, 199.231.78.0/24, 64.62.142.12/32, 209.206.48.0/20   7351 UDP outbound Meraki cloud communication Access points, Cameras, MX Security Appliance, Switches Your network(s) 209.206.48.0/20   80, 443, 7734, 7752 TCP outbound Backup Meraki cloud communication, Backup configuration downloads, Measured throughput to dashboard.meraki.com, Backup firmware downloads, Meraki cloud communication, Splash pages Access points, Cameras, MX Security Appliance, Switches Your network(s) Any   123 UDP outbound NTP time synchronization  Access points, Cameras, MX Security Appliance, Switches Your network(s) 8.8.8.8/32   53 UDP outbound Uplink connection monitor MX Security Appliance Your network(s) 8.8.8.8/32, 209.206.48.0/20     ICMP outbound Uplink connection monitor MX Security Appliance   ... View more

For a small size company WAN topography with just a few sites only needing class C subnets to cover the end node capacity per site, like my situation, I Love the site specific 2nd octet /16 LAN sub-net concept. Wish I would have done that many years ago when we put in VOIP... Too bad now, I would have to redo my subnets, A lot of extra work...   Makes a lot of sense if one wants to break up broadcast domains via adding more vlans... i.e. back office Servers vlan, workstations vlan, VOIP vlan, IOT vlan, wireless mash vlan, segmented fiber linked vlans between out-buildings... I may plan this concept for the next network re-organization project ... ... View more