Yes, especially when replacing MR52s and trying to reuse the three screws into the plasterboard ceiling that were fine for the MR52…  Not usable for a CW9166I!   Mind you, the CW9163E is even heavier, it feels like it is hewn from a solid billet of metal, lovely hardware! ... View more

I think it will depend on what you're looking to achieve from the integration. The standard set of Bluetooth tools are covered here: https://documentation.meraki.com/MR/Bluetooth/Bluetooth_Low_Energy_(BLE)#Bluetooth_clients If you need to explore anything else, in great depth, I suggest you reach out to your Meraki account team.    Contact details are available through the Dashboard under  Help (or ?)   Top right    > Get help >  Still need help? > Contact your Meraki sales representative ... View more

Hi Philip,   Thank you so much. I will check this out.   ... View more

Puede dejar el conmutador en el inventario; solo asegúrese de que no esté asignado a una red. ... View more

Ok, so Layer2 is out of the question.  That's fine.  These devices will connect to the server as long as there are routes setup.  So I can have the server on a different subnet, as long as it's in the same network.  Like, I think I should be able to do this through the site-to-site VPN.   ... View more

Initial provisioning can be done with a wired connection or a provisioning SSID.   Note you can only use a single MDM on a device.   Microsoft Intune has recently released an interesting option, Cloud PKI.  This should work with "Local Auth" certificate authentication on the MRs (disable passwords for this configuration). https://www.microsoft.com/en-us/security/business/endpoint-management/microsoft-cloud-pki  https://documentation.meraki.com/MR/Encryption_and_Authentication/Meraki_Local_Authentication_-_MR_802.1X#Certificate_Caching_(Certificate_Auth)  ... View more

As previously;  opening a case with Meraki Support is really the way to go with such things.   You're best off calling on the telephone, generally - email / dashboard takes a long time in back and forth questions and answers. Contact numbers are available via Dashboard:   Help (or ? top right) > Get help > Still need help? > Call the Meraki Support team ... View more

Yes exactly that.   Reserved IP is taking those IP addresses out of the DHCP scope. ... View more

Whilst agreeing with the recommendation for MX / Z devices everywhere (😉) I think the original ask was for all the tunnels to be non-Meraki VPN, in which case the limitation around not hairpinning AutoVPN with non-Meraki VPN doesn't apply.   I've not come across this particular ask before though - where there are no Meraki Spokes (as I understand it) - so am seeking some answers internally on whether this will / should work.   Did you raise a case with Meraki Support?   Did the Dashboard throw up errors, when you tried to configure it - or did it just not pass traffic?  Were you able to use packet captures to see where the traffic flow was breaking down? ... View more

@GreenMan is right. Be sure to use MST 0 (instance 0) for compatibility. This was discussed before on this other thread. ... View more

Thank you all for your information. Given the high costs, I think I will be sticking with the manual moving patch cables to the second switch.  ... View more

Indeed Phillip,  Sad but probably true... ... View more

With hindsight, you're right, sorry    (I only have an MG21 personally, where it is an LSP option). I raised this with product line and it is planned for addition to MG51 (and MG41) at some point, but with no fixed timeframe for availability, just now.   I have asked the team for an update, which I'll share when I can. ... View more

And udp/500.  🙂 ... View more

>the EC2 instance I cant ping back to an internal ip   Try temporarily disabling Windows Firewall on the internal machine to make sure it is not blocking the ping.   Make sure the on-premise MX has the VLAN where the internal machine is located included in AutoVPN.   ... View more

A factory reset will remove the config, but once the switch checks back in, it will re-apply the saved config assigned for that serial number, in the Network in which it's logically deployed.   If you want the switch to not load a duff setting, remove the duff setting in Dashboard, before it checks back in.   You may (also) find switches reverting to a locally stored Safe Config, if they can't get back to Dashboard any other way.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Behavior_during_Connection_Loss_to_Cisco_Meraki_Cloud#MS_switch ... View more

@hillster do the drivers have a version number? ... View more

This is a frequent issue lately ever since we made this change back in Nov 2023.    "API interactive Documentation update Improved security by providing test keys to run request against the API and restricting user sensitive API keys to be pasted in the documentation."   The default API key is for a sandbox environment Org   For example this call works https://developer.cisco.com/meraki/api-v1/get-organizations/ because it simply returns the Org the API key has access to.   "id": "1215707", "name": "API Demo Organization"   But when you run other endpoints that specify an Org, networks, etc that API key of course wouldn't work in your own Org. So, as @bbyw mentioned you need to add your API key if you want to use the dev site against your own Org.    One more example using the get Org networks call. If you put your Org ID in it will produce a 404 error because the default API doesn't have access to your Org. If you instead used the demo Org ID mentioned above 1215707 the call works as expected. ... View more

Yep, given the available info, I would say so  👍 ... View more

Raise a case with Meraki Support ... View more

There can occasionally be geo-specific restrictions on capabilities,   e.g.  https://documentation.meraki.com/General_Administration/Support/Information_for_Users_in_China#Unsupported_Features_in_China I've done a little bit of digging (Africa not my patch).   There can be challenges around MX - particularly with it's VPN & other security capabilities - in some countries.   The recommendation would be to work closely with an authorised Cisco reseller with specific experience in-country.    You'd not get any such help purchasing in the US and trying to import.  I can certaily foresee challenges for you, in going down that path. ... View more

The way most companies / organizations achieve this is to use authentication via 802.1x at the point of connection.   The identity used will be assocated with the device in question, in the Dashboard.  Of course, that's just a side-benefit for most customers, as it's mainly done to confirm who or what is connecting to their network and to provide fully secure WiFi comms.  Such identity is often also used to apply different policies to different users or user groups too;   i.e. what resources can they access?   how much bandwidth can they consume?   etc.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies Enterprise 802.1x is a pretty big project to undertake though, so best to explore this with an experienced Cisco partner, I would say.    ... View more

Bear in mind that, even if your core switches are a stack, uplinks will not loadshare unless you also configure them as aggregate links - otherwise a loop is formed, which Spanning Tree will resolve by blocking links. ... View more

Both Legacy and Free 100 will be going entirely - at least, in terms of enrolling new devices.  If you want Systems Manager capabilites for new devices after 7th Feb, you will need to purchase the appropriate quantity of licences.   These can be ordered using a SKU of the form LIC-SME-xYR    where x = the number of years (1, 3 or 5).   The quantity is determined by the number of devices you wish to manage using Systems Manager. https://documentation.meraki.com/SM/Other_Topics/Meraki_SM_Legacy_and_Free_100_Retirement_FAQ As per this document, Meraki support for both Legacy and Free also end on this date. ... View more

Picking up on Karsten's point...   you mention it's for a new site.    Which doesn't sound like you intend it for a cloud platform like Azure or AWS (?)  What you can't currently do is run vMX on a hypervisor like ESXi or Hyper-V.  Nor (as the lack of Adv Sec license would imply) can you currently use it as a UTM for your cloud platform.  For the time being it's used to provide secure access to your cloud platform from your MX-based SD-WAN solution. ... View more