Could you post the outside interface of your ASA, obfuscating the 2nd and 3rd octets? ... View more

This is suggesting the appliance has not got an Ethernet connection.  Have you definitely got a link light?  Have you tried a cross over cable? ... View more

Don't do that.  You create the exposed node problem. https://en.wikipedia.org/wiki/Exposed_node_problem   Lets say one client can see both antennas, while another client can only see one of the antennas.  You can get the case where one client can't hear the other - so while the first client is busy transmitting the other one starts and clobbers the signal - killing it. ... View more

I don't understand.  Restore from what?  Or do you mean re-enrol it back into Systems Manager? ... View more

@Dashboard_DJ I think using a KPI of requiring 20% of your customer base to be using a software image before it is made available as a stable release is not appropriate.  This KPI causes Meraki to promote the use of new beta firmware to its customers - thereby encouraging them to use software not yet considered stable - in production environments just to get to that KPI.   I understand the intent of the KPI - but I think the KPI will cause more grief to customers rather than its goal of producing quality releases. ... View more

It doesn't matter what other vendors do when you are using Meraki kit ... ... View more

Very clever. ... View more

I agree entirely!!! Stop blasting us about beta firmware updates and give us more timely production releases. ... View more

I think there is some confusion with the term "non routable ip" and "private ip".  These are not the same thing.   Lets get more specific.  Please obfuscate the 2nd and third tuples.  So if you had an IP address of 10.11.12.13, please describe it as 10.x.x.13.   What is the IP address, subnet mask and default gateway you are trying to use? ... View more

I wish there was a way to all the API from a "front end" page, rather than having to do it from a back end.   It would be great if you could define a CORS domain in the API key section. ... View more

That did the trick thanks! ... View more

Here is something else to try.  Can you configure an ordinary computer with the static settings and plug it into the Internet feed directly and get that to work?  If not, you can take that back to your internal support people - as they can't complain that this case wont work. ... View more

That sounds like a bug. You might be able to create a network manually and then bind that network to the template. https://documentation.meraki.com/zGeneral_Administration/Templates_and_Config_Sync/Managing_Multiple_Networks_with_Configuration_Templates#Binding_Networks_to_a_Template ... View more

An MX can work with either a public or private IP address on its WAN interface. The only requirement is that it can talk to the Meraki cloud on the Internet. You can copy your 5512 "outside" interface settings to the MX, even though it is a 10.x.x.x addressing. However you also need to specify some reachable DNS servers - otherwise the MX wont be able to do a DNS lookup to get to the cloud. You might have some specific ones you are allowed to use, or you might be able to use Google's, 8.8.8.8 and 8.8.4.4. And obviously you need to specify the default gateway which is the same as the default route on the ASA. If the MX is not coming up connect to the local status page and see what error it is reporting. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#MX.2FZ1_Series If the ASA has a VLAN tag configured on its outside interface make sure you configure the same tag on the MX WAN interface. Does your Meraki MX plug directly into your default gateway? If it doesn't then you'll need who ever is in charge of the default gateway to do a "clear arp" on it. Otherwise the default gateway wont know that the MAC address for the assigned IP address has changed. ... View more

An MX can work with either a public or private IP address on its WAN interface.  The only requirement is that it can talk to the Meraki cloud on the Internet.   You can copy your 5512 "outside" interface settings to the MX, even though it is a 10.x.x.x addressing.  However you also need to specify some reachable DNS servers - otherwise the MX wont be able to do a DNS lookup to get to the cloud.  You might have some specific ones you are allowed to use, or you might be able to use Google's, 8.8.8.8 and 8.8.4.4.  And obviously you need to specify the default gateway which is the same as the default route on the ASA.   If the MX is not coming up connect to the local status page and see what error it is reporting. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#MX.2FZ1_Series   If the ASA has a VLAN tag configured on its outside interface make sure you configure the same tag on the MX WAN interface.   Does your Meraki MX plug directly into your default gateway?  If it doesn't then you'll need who ever is in charge of the default gateway to do a "clear arp" on it. Otherwise the default gateway wont know that the MAC address for the assigned IP address has changed.     ... View more

I've never done it, but I don't see any issue with that. You could also use tags for this purpose (creating a tag per division) and assign those tags to the devices. ... View more

I don't know. I'm not saying it wont work, but I am not very confident that it will. Adding an ASA 5506 will be rock solid reliable though. ... View more

Can you do this style connection (my preferred option)?             Internet                |       +------+-------+        |                  |        MX            ASA         |                 |         +------+------+                  |          Inside network   ... View more

I'm not confident that is going to work.   Normally the site to non-Meraki site VPN is for subnets directly connected to the MX in question (and which you have specifically enabled).  I am not confident you can build the VPN to routes sitting in its routing table.   What I did for one of my customers is put in a little ASA 5506 beside their MX hub.  I added static routes on the ASA 5506 to get to all the remote MX's via the hub MX.  I then added a route to the MX hub for the remote VPN via the ASA 5506 and included this in the AutoVPN.  I then built a VPN between their 5506 and the remote non-Meraki VPN peer. They actually had a few more complex site to site VPNs as well, include one that needed a NAT - so the ASA 5506 was the only "nice and clean" solution for them.   Perhaps this might be an option for you as well. ... View more

I typically create a combined network per physical site for all the Cisco Meraki physical hardware. I typically create one Systems Manager network for the entire organisation. ... View more

Can you build the VPN from the two Meraki's to the non-Meraki - rather than only from the hub?   That will make things much simpler. ... View more

Try giving it a power cycle.  If it doesn't check back in try giving it a factory reset.   https://documentation.meraki.com/zGeneral_Administration/Support/Resetting_Cisco_Meraki_Devices_to_Factory_Defaults#Indoor_Access_Points_(MR1X.2F2X.2F3X) ... View more