Two things: are all of your AP's in one big Dashboard network? What do your switch port configs look like for the AP's?  ... View more

If you feel this is a load balancing issue on the AP's, it may be worth trying the 25.5 firmware which includes client load balancing across AP's. We have a few thousand Chromebooks that don't have a problem with MR32/34/42/52's.  ... View more

You may be able to override the template IP addressing on the specific network. Try creating a test MX network and applying your template to it. See if you are able to change the IP scope on the Addressing & VLAN's page. Templates allow you to override certain things locally, but I'm not familiar enough with MX templates to know what they allow or don't allow.  ... View more

I'm currently using firmware in the 14.X range on MXen without any problems. I'm not sure what the highest firmware available is to your network(s), but I wouldn't be afraid to try some of the very recent versions if you have them available.  ... View more

I'm able to compare two networks that each have an MX64 in them. I'm also able to compare an MR template network with a standalone MR network. Might be worth opening a support case if you're seeing different behavior.  ... View more

I believe config sync only works with MR and MX networks. And if you are using config templates, then only the templates will show up for config sync.  ... View more

We also saw this with an MV21 in the US that is mounted about 1' above a light. Seemed to not be as noticeable after adjusting the focus a bit, but it's still there at times.  ... View more

This is not currently supported on any Meraki product. You can submit a wish for it though.    Many people will take screenshots of the config pages as their backup strategy.  ... View more

Beta is a term used pretty loosely by Meraki. Many customers are running "beta" firmware. I'm currently running beta firmware on MX600's in production serving ~20,000 users.    If you upgrade and run into issues, you can roll the firmware back without needing help from Support with the new firmware management tool.  ... View more

I'd recommend trying the latest beta firmware. This is very likely what Support would suggest you do as well.  ... View more

Organization -> Firmware is where you can see the actual version numbers.  ... View more

As long as you create the /30 interface on the switch first, it will correctly use that as the default route for all other L3 interfaces you create. You should still set the MX's gateway as the /29 block IP you assign to the MS225 though.  ... View more

Yes, you can have other devices on the switch as long as they’re in another VLAN. Create a L3 interface with the /30 from Comcast and assign a unique VLAN to it. Put a port in access mode in that VLAN and plug the Ciena into it. Create a second L3 interface with the /29 from Comcast and use a different unique VLAN. Put another port in access mode in this VLAN and plug the MX Internet 1 port into this port. Assign the MX an IP from the /29 and there you go. You can then use the remaining IP’s in the /29 (minus the MS225’s IP and MX’s IP) for 1:1 NAT rules. ... View more

Comcast EDI has been really nice for us. Very fast routing to Netflix, Apple's CDN, etc. which is great for our use (K-12). We're adding a second circuit later this week that will go to Hurricane Electric.  ... View more

Yep, that should work since the MS225's support 16 static routes. Just make sure you create the /30 interface first so the default route is set properly.    Also keep in mind you'll still need to get the MS225 Internet access through a non-routed interface. So just plug it into your internal network in your usual management VLAN in addition to the Comcast interface and the MX interface.  ... View more

You'll either need to place a L3 device in front of the MX which can handle this type of setup, or ask Comcast to provide the /29 as the handoff and skip the /30. This is a limitation of the MX line. Our solution in the past was to put an MS320 in front of the MX and create two L3 interfaces on it - one with the /30 for the Comcast handoff, the second with the IP space Comcast was routing to us.  ... View more

There's probably some awful peering between AT&T and Comcast along the way that's causing the very slow upload.  ... View more

If you're distributing enterprise apps, then you need to either have the individual devices included in the provision profile, or sign them with the enterprise distribution cert which will allow install on any device.  ... View more

What's the event log on a client say? Did you confirm on a client with RSOP.msc that the GPO is applying?  ... View more

You don't need to use the Enterprise dev account with the devices for SM to work. That's only for use with enterprise app deployment/development.    You also don't need to use Apple Configurator. SM works on its own.    If you are using VPP, is your server token expired? This is found on the Organization -> MDM page under "Apple VPP Managed Distribution".  ... View more

Stacks dropping their uplink (and then doing absurd things afterwards) is a well known issue on the MS team from what I've gathered. The uplink being dropped is specifically called out as a bug fix beginning with firmware version 9.27 which was just released.  ... View more

What firmware version are you using? The current stable MX firmware version is quite old at this point and seems to have plenty of bugs, especially with advanced L7 features & advanced security features.  ... View more

I have two MX600's in production in warm spare mode. These are used for firewall/NAT for ~20,000 users/10,000 devices. In total the upstream bandwidth is 4Gbps. We also do two site-to-site VPN tunnels, one is Meraki and the other is an ASA. Plenty of client VPN connections too without and problems.    If you want to do a real world speedtest through my MXen, here you go: readingsd.speedtest.net ... View more

@Welles Nope, no tags in use for the SSID that disappeared.  ... View more

@tmburke I don't believe the issue I encountered with MR33's is currently noted as a known issue. I was told that it is noted internally as a known issue but was unable to find it publicly stated on any of the currently available firmware versions.  ... View more