ICMP traffic doesn't obey the preference, it goes out of the primary link as you've seen.  If you can monitor http response time then that should work. ... View more

That's the problem. the field won't set back to empty if you set the secondary concentrator as "none" and toggle it back on. The field is buggy and won't reset back to empty. I also wanted to see what would happen while its empty. ... View more

  1. I use both operations: getNetworkClientsUsageHistories and getNetworkClientsApplicationUsage.   2. getNetworkClientsUsageHistories also has the same problem with the same Cisco clients.   It happened when I used timespan=1000 and when I used timespan=7200.   In the case I opened, I put all the needed information (net ID, client IDs), but I got strange responses from the support team.    As far as I understand, there is a bug in those 2 endpoints. There are 2 options to fix it: 1. Remove the problematic devices from the client list of getNetworkClients. 2. Or ignore the problematic clients when responding to getNetworkClientsUsageHistories or getNetworkClientsApplicationUsage.   If the Meraki R&D team has a better solution - welcome!     p.s. I found a real bug. Why does no one give me kudos? ... View more

Update from support:   Being that our AI Assistant feature is still in the test phase, we are still working on some of the configuration aspect and working out some of the bugs on the backend. I have brought this issue to the attention of our senior management team to take a look at on the backend. In the meantime, can you try adding the following subnet ranges to your login IP configuration? • 64.62.142.12/32 • 158.115.128.0/19 • 209.206.48.0/20 • 216.157.128.0/20 ... View more

KUDOS to @alemabrahao and @Mloraditch!!! ... View more

Pretty easy.   1- GET Policy objects 2- GET EDL : https://saasedl.paloaltonetworks.com/feeds/m365/worldwide/any/all/ipv4 3 - PUT Policy objects with content from step 2 4- Profit     Voila.     ... View more

@outram ... View more

Audio beacon / location identification for MR access points we have a hard time locating these in some of our older locations and visual flashing only works if you can see the device Think Apple “Find My” audible alarm to locate APs ... View more

As has been said above, Bridge mode is the only way to do it. As much as Meraki NAT is great, as soon as you have any additional requirements it becomes a bit of a hassle. I typically use bridge mode and configure L3 firewall rules on the SSID to block access to RFC 1918 IP addresses, allowing only the shared resource clients need to access (Eg. printer/print server) and internet locations. ... View more

Yes , that's why the 2 links on sw#2 are in blocking as illustrated.   This only works in theory as I explained higher. ... View more

Here is the missing context :          ( this is a validated Meraki design btw )    We have sites that have 2 MXs.   MX A routes red vlans  MX B routes green vlans. Switch "sees" / samples everything.   When you perform GetNetworkClients on Network A , since it contains the switch you will get EVERY clients even if they are not routed by MX A. This is something you CAN exclude from the client page on Network A ( from the dashboard ). But you CAN'T do that with the API.   Hope that helps. ... View more

@JamesT91 Sometimes we are speedy 🙂 We just want to fit in!! 🙂 ... View more

I think for now the best platform is to use Launchpad until things sync up better 🙂 I'll be adding some org-wide group policies in that org to present a better demo today. ... View more

Upgraded APs at our two office locations. Hope there will be no major BUG. ... View more

The MR55 negotiates power dynamically based on its current needs. It may not always draw the maximum, for example, if not all radios are active or under heavy load. ... View more

Great info, thanks! I’ll have a dig into it and see how I get on. ... View more

have you deployed any MX as HUB in routed mode with DC-DC failover ? where both DC advertise similar routes. ... View more

    Ms130 fixed issues Fixed a bug that caused some MS130 switches to fail to provide PoE when running MS 17.2.1   Seems they may have updated the changelog since it was initially posted here - the above item is now also shown on our dashboard.    I haven't checked the rest of the changelog for any differences - just spotted this one as we're dealing with some PoE quirks on an MS130.  ... View more

Well that didn't take long to sort out. 🤣 Thanks for the update! ... View more

And for what it's worth - I attempted to point out the "consistency" aspect as you mention on the post below (i.e., advantage or advanced).   Documentation Digest: May 23rd - May 27th, 2025    Perhaps it's taking a bit of time to morph the changes to be consistent throughout. ... View more

Woohoo !    https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Roaming_Technologies   Mandatory DHCP + Fast roaming (802.11r) This feature enhances client mobility by enabling support for Fast Roaming on SSIDs where Mandatory DHCP is enforced. Starting with firmware version MR 32.1.X, DHCP state information is now shared across APs, allowing seamless client transitions between APs without reinitiating DHCP requests. Prior to MR32, client roaming to a new AP was required to send new DHCP request before traffic would be allowed. Even if the client had successfully obtained a DHCP lease from the previous AP, the new AP would block traffic until it saw another DHCP exchange.     RFC compliant ! ... View more

In this case, if I am right, the message depends on the role that the MX is playing (as you noticed). MX as DHCP server → no DHCP lease available MX relay → no_offers_received So I believe the same applies to the MR since it is not acting as a DHCP server.   Is it possible to test? ... View more

Which firmware are you running? Are you using WPA2-PSK, WPA3-SAE, or something else for this SSID? ... View more

Hooray!! ... View more