Could be the case that the devices are having difficulty connecting to the Hidden SSID.  Try un-hiding and seeing if the IoT devices are able to connect or not. If they can you might be able to get away with hiding it again and having them stay connected. ... View more

Guessing you replaced the {organizationId} already in the URL? ... View more

Just curious, what functionality are you missing/looking for? ... View more

Hey; Your Org ID can be found on the bottom of any page in your Meraki Dashboard. 404 is most likely it didnt find the org with the ID you didn't put in. Append this where it shows {organizationId}  in the URL for the request. If you are still struggling go through the basics before proceeding any further. https://developer.cisco.com/meraki/api-v1/introduction/#meraki-dashboard-apis   ... View more

Not sure if this is what you mean. Can fetch both WAN IPs; Gateway and Status https://developer.cisco.com/meraki/api-v1/get-organization-appliance-uplink-statuses/ Then sort as needed. ... View more

Shouldn't take long if this is not the first boot.  Anecdotally would say its no longer than 5 minutes.   ... View more

Finally here in my EU Instance 👀   ... View more

Firmware update or raise a ticket with support. ... View more

Hey; Would check to make sure you are assigning the rule to the correct SSID.      Wireless > Configure > Firewall & Traffic Shaping Source: https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Configuring_Simple_Guest_and_Internal_Wireless_Networks       ... View more

Doesn't look like its supported. https://meraki.cisco.com/products/wi-fi/models/ https://www.cisco.com/c/en/us/products/collateral/networking/wireless/wireless-lan-controllers/nb-06-cloud-mon-catalyst-faq-cte-en.html Cant find it here either. https://documentation.meraki.com/MR/MR_Installation_Guides   ... View more

More docs you'll find relevant: https://documentation.meraki.com/General_Administration/Inventory_and_Devices/Moving_Devices_between_Organizations   ... View more

Hey Chema; Based on the documentation Removing an MX from its former network and moving it to a new network will wipe out the existing configuration on the MX, that it had from its old network.   Since you are unclaiming it; it should revoke all config. You'll need to then manually add the static IP like the previous setup. Here is the linked doucmentation: https://documentation.meraki.com/General_Administration/Inventory_and_Devices/Moving_Devices_between_Networks   ... View more

Hey; In the event of issues arising from new firmware you can Rollback directly from the Dashboard. They do not give details as far as how it is performed on the device itself if thats what you are wondering. https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Managing_Firmware_Upgrades#Rolling_Back_a_Recent_Firmware_Upgrade   Rolling Back a Recent Firmware Upgrade Firmware upgrades can be rolled back to their previous version up to 14 days after an upgrade takes place. Follow the steps below to roll back a firmware upgrade. Navigate to Organization > Monitor > Firmware upgrades. From the Overview tab, view the Most recent upgrades section and find the applicable upgrade entry. Click on the applicable upgrade entry where it lists the number of networks and devices that were upgraded. Click the Rollback button. Select a reason for the rollback and enter a brief description. Select Perform the upgrade now or Schedule the upgrade for, specifying a date and time for the rollback.  Click Submit to schedule the rollback.  Best Deployment strategy is to move a handful (or single) of APs into their own Network Dashboard to roll out firmware upgrades as it cannot be done per device but per network. Example from docs: https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practices_for_Meraki_Firmware In the case of failure then a Support Ticket should be raised anyways.   ... View more

According to the docs; you should be able to unbind and retain the configuration including local network overrides. https://documentation.meraki.com/General_Administration/Templates_and_Config_Sync/Managing_Multiple_Networks_with_Configuration_Templates This should be the case for combined templates as well as far as I can tell.       ... View more

Would be best to understand the rules of binding and unbinding of templates works e.g. unbinding and retaining configuration as well as what can be overridden locally for each site. Of course the consensus for deployments is generally making sure you have a testing process in place that suits you. E.g. Unbinding Site and retaining Config > Making adjustments > Monitoring Impact on-site > Accept/Reject > Consider impact on all affected sites > Make changes to Template and Bind Test Template back. https://documentation.meraki.com/General_Administration/Templates_and_Config_Sync/Managing_Multiple_Networks_with_Configuration_Templates   ... View more

Hey; Not sure this topology is fully supported by Meraki but I think I understand what you are getting at. Could be possible to set the SiteA Core Switches as uplink/backup WAN for the SiteB MX using the 3rd backupWAN feature available (vice versa). https://community.meraki.com/t5/Security-SD-WAN/New-MX-feature-MultiWAN-Backup-Uplink-third-backup-WAN/m-p/226250 In Theory it could work but there are some limitations. Could also explore the possibility of adding a third redundancy line with MG Wireless WAN if the above is not an option but you want to cover all bases uplink wise. ... View more

Hey; Interesting connection you have there.  I would read up more on this article. For this to work you would need VRRP traffic to pass through from one MX to another. From your Diagram looks like you would need another connection between Site A's firewall to SiteB's Core Switch and vice versa for the recommended setup. That being said for each Site on the Management VLAN; Security & SD-WAN > DHCP; Manually set the IP addresses for the core switches respectively. However this assumption is that they are under the same Network in the Dashboard.   ... View more

With NAT mode you might struggle there. The AP runs the DHCP Server so there is not really much you can do from this point as you cant route traffic in anyway. One limitation there. If you use WPN on the network you can achieve the same type of client isolation however this only works when using Identity PSK without Radius. Splash Access also has some solutions for this. I managed to by pass this by segmenting the printer onto a different VLAN (if wired) and allowing in the 'User' SSID, Wireless > Access Control > External DHCP Server Assigned > Bonjour Forwarding to allow Printer Traffic. This does mean you have to switch to bridged to break the limitation.  ... View more

Are you refering to to EA release of Access Manger?  There are a couple new videos on the Meraki Minute Youtube channel that take you through the module as well as setting it up for your MR Devices and MS devices. Configuration guides are here: https://documentation.meraki.com/Access_Manager/Access_Manager_Configuration_Guides More detailed guide below: https://documentation.meraki.com/Access_Manager/Access_Manager_Configuration_Guides/Access_Manager_Username%2F%2FPassword_Authentication_-_EAP-TTLS%2F%2FPAP_with_Entra_ID_Lookup   Configure endpoints for username and password authentication Configure Entra ID integration to synchronize users, user groups and user attributes Configure SSIDs and Switches to use Access Manager Configure authorizations to be used – SGTs, VLANs, Group Policies and others  Configure Access Manager rules for policy evaluation ... View more

I WANT IT ... View more

Documentation states they are rolling-out starting with the Americas.  Region based roll-out means the rest of us have to wait a little longer.  Non-commital on the timeline I imagine. ... View more

Where do you find the option to configure a different IdP other than Entra? Selecting the "+Create IdP" forwards me to an Entra ID configuration page and doesn't give the option to configure anything else. As far as I can tell the documentation remains vague about other 3rd party providers. Assuming it might be a Feature Flag you need to request them to enable? ... View more

Somewhat more stable at least in my environment compared to the networks that are not setup in HA. However that is just my anecdotal observation. Assuming on our end they just happened to occur at different times. ... View more

With AMP disabled but IDS/IPS Detection enabled we noticed issues. FW-18.211.2 Devices with this disabled didn't experience the restarts. After we made this changed we did not experience issues with our MX devices but not sure if this coincides with any hot-fixes they are currently pushing. Can confirm from our side as well that After Event Intrusion Detection Rules Updated - snort_rules_version: 20250414-2221; there was a VRRP transition event and the MX rebooted. HA networks seemed relatively stable but others not so much. ... View more