I haven't noticed this on either of the MV12's I'm testing (a W & N). Are you on 3.4 firmware? ... View more

Even if you enable motion based retention (which you probably would want to), you always have 72 hours of footage available.    https://documentation.meraki.com/MV/Video_Quality_and_Retention/Motion-based_Retention ... View more

@btrask The Quarterly Update was today.  ... View more

@jwwork Multicast routing & IGMP snooping are disabled. Flood unknown I believe is on. Cisco phones do participate in the paging along with the Valcom units.  ... View more

@jwwork I've needed to disable IGMP snooping on Meraki networks with Valcom speakers. Might want to give that a try.  ... View more

It might be worth checking with Support to see if there is a known issue moving devices between orgs on whatever firmware version you're running.    It's probably also worth making sure the MX firmware version is set to the same version between the orgs.  ... View more

For Windows, @PhilipDAth is correct. You could deploy the cert via GPO and configure it as trusted for the SSID.    For mobile devices, you'd need to use an MDM solution (such as Systems Manager) to deploy a profile that includes the certificate and SSID info. Neither iOS or Android will trust certs for wireless by default without a profile telling them to do so.  ... View more

Can you have someone at the remote site plug into the management port (if the MX model has one) and see if the static IP info is still there? Sounds like it was wiped out for whatever reason during the move. Otherwise I'd go with @PhilipDAth's suggestion and do a factory reset (which will require the static IP info to be put back in place on site).  ... View more

A new stable release candidate is available now as 25.11. Anyone want to give it a try that was seeing the issue with Windows machines?   New HSRP support for Bridge Mode Layer 2 client isolation Bug fixes AP spoofs not being detected. (MR52/72) A corner case where AP broadcast on W52 channel when in site survey mode (MR84) A corner case where AP would stop broadcasting SSID (MR30H/33/42/53/53/74/84) A corner case causes AP to reboot (MR18) A corner case causes AP to stop responding to clients (MR32) A corner case causes APs lose connectivity to dashboard until reboot in certain cases (MR33/74) Known issues Condition under investigation that causes VoIP RTP packet loss (MR42/MR52/MR53) Condition under investigation causes 2.4GHz radios to become unresponsive (MR32/MR72) Condition under investigation causes radios to become unresponsive for 5 seconds in high density networks (MR34/MR32/MR72/MR26) Condition under investigation causes lower than expected throughput on the 2.4GHz radio (MR26/MR34) Other General performance and stability improvements. ... View more

This may be a way to stop people from issuing an update command to 11.3 which then breaks MDM communication.  ... View more

Group policies work with MR and MX products. They're set at the network level (Network wide -> Group policies). You won't have any issues using them with just an MR network.  ... View more

The MX line does not support IPv6 currently.  ... View more

@j5428 I'm now running 14.25 and the frequency has been greatly reduced to only one or two reboots per week now. I'll also note that all of the S2S VPN peers are on 14.25 now as well (one MX64, one Z3 and one vMX100).  ... View more

@Benn Interesting that you also are seeing issues with DNS on the 425 platform. An engineer I spoke with today ran a packet cap for 2 minutes. Of the 100,000 packets in the capture, over 90,000 were DNS - the vast majority of them malformed requests (coming from MR42’s & 52’s).    He also did a capture from another network where the only difference is an MS350 core instead of 425 and didn’t see the issues.  ... View more

@Leejohn1 wrote: What is the recommendation for this? 🙂   Roll back your firmware to the last known good version.  ... View more

Unfortunate update on this: the root issue has not been resolved. It appears there may be something going on with malformed DNS requests from MR devices that is overwhelming the MS425 CPU.  ... View more

I recall this being a memory exhaustion issue back on 13.X. This is no longer an issue on 14.X if you want to upgrade. Perhaps this is another bug, but I had this issue previously.  ... View more

I'm continuing to see this issue in 25.8 although much less often than 25.9/25.10.  ... View more

@Swong You can email merakinow@cisco.com for details. I suspect the answer is yes within reason.  ... View more

This seems like a repeat of your original thread in the MX forum (where it should be) here: https://community.meraki.com/t5/Security-SD-WAN/Route-connection-changes/m-p/16208#M3935 ... View more

I have only ever implemented one LAN link between an MX and a core switch sitting behind it. MX units support warm spare for redundancy.    Perhaps @PhilipDAth has some insight on this.  ... View more

The MX does not support creating a link aggregate on its LAN interfaces, nor does the MX participate in STP. So what you are doing is creating a loop between the MX and your Cisco core. Your Cisco core should be blocking one of the links with STP assuming you have STP configured on the Cisco core.  ... View more

Right, because it's the domain I'm running on my DNS server.    The devices will register in DNS if you allow dynamic updates on your DNS server. The domain suffix is provided as a DHCP option.  ... View more

The device name configured in Dashboard is appended with the device's MAC to create the hostname.    Here's the PTR record for the device I took a screenshot of: test-ms225-0c8ddba48c28.domain.com ... View more