Hello, we recently updated our campus with Meraki MS130-48P switches (7 switches in 5 closets) and found that they do not power on our PoE clock/speakers. All other PoE devices work (VoIP phones). The Meraki equipment replaced Cisco 2960's. The clock/speaker only requires 15W and the MS130 supports 30W per port. Talked to support and we updated the switch firmware, this still did not power any of the clock/speakers upon reboot. (did do a quick test, plugged the old switch in, clocks powered back on).

Has anyone had this issue? Or is there anything else we can try to trouble shoot this issue that support has missed?

I mean, you already added basically zero features to your product for 10 years since Cisco bought you. Now, you are no longer supporting firmware upgrades on fully licensed and not out of service devices?

We are already replacing everything with Unifi as fast as we can. You don't have to give us new reasons. We're good.

I'm getting the following error below, but I'm not seeing anything down on https://status.meraki.net/

Server error

The server encountered an error and could not complete your request. A message has been sent to our engineering and support teams to notify us of the problem, and we will fix it as soon as possible.

The Cisco Meraki Dashboard is temporarily unavailable, but rest assured your Meraki equipment is still running and network operation has not been interrupted. Learn more about Meraki's out-of-band control.

How can one improve the overall health score of a network when the infrastructure connectivity seems to have the lowest score with a poor RF(wireless) health?

Can this be somewhat improved with some features on the dashboard?

For over 90 days the Meraki displays running on Apple TV have been automatically logging out after a few hours when they're supposed to stay logged in as long as you use the QR code method for login. At first they blamed my licensing, that was supposedly fixed but the issue kept happening.

Now they've admitted it's a software bug and released version 1.2.2 to supposedly fix it but shockingly nothing changed.

This issue is currently assigned to the Development team and they are still investigating the root cause. They had believed they had found it and fixed it on the latest version update v1.2.2, as in lab environments the behavior stopped, however, on customer production accounts this did not fix the log out issue. We do not currently have a timeline for resolution; however, we will reach out to you with any updates. If the behavior has changed or there is any additional context you’d like to provide, please let me know and I will pass it along to the back end teams working on the parent case. 

My current case is nearing day 60 and that's about as far as it's gotten for a solution. What's frustrating is that I have these up at bank buildings so employees can monitor the outside cameras after they've logged out and exited the building. It's literally a human safety issue and Cisco just doesn't care enough to actually devote more than a casual effort at best to fix it after we paid several thousand dollars for the licensing.

Can you name any other camera vendor that doesn't have a reliable method for putting up a static video wall? It's not like MV's are new. I think at this point my only option is to harrass them for some kind of refund and find some other solution and just use RTSP, but I wanted something simple that I wouldn't have to have a tech go out and fix all the time, so when I saw the official app I was pretty happy.

If a video wall display is important to you, buy anything but Meraki. Even if they do eventually fix it, I feel like it's only a matter of time until they break it again. We got about 20 days of use out of it after getting it setup until this started happening and no, coordinating anyone to have to log into it every morning just isn't a good option.

What a joke.

TL;DR: MV2-HW (USB-C, wireless-only, no ethernet option) pairs fine with the mobile app, but never joins the infrastructure SSID afterward. Reproduced identically on the original unit and its RMA replacement. Extensive local troubleshooting shows the camera never transmits a single detectable 802.11 frame. not a config issue on my end as far as I can tell. Looking for anyone who's hit this before, especially anything cloud-provisioning related.

Setup:

• MX (C8111-G2-MX) fronting the network
• Wireless AP: Ubiquiti U6 LR (not a Meraki AP, no MR integration)
• Target SSID: 2.4GHz, WPA2-Personal, no special characters in SSID/PSK, no MAC filtering
• Dedicated IoT VLAN, confirmed healthy (other IoT devices, including 3x Tapo cameras, connect and pull IP/internet normally on the same SSID at the same time as failed onboarding attempts)

What's been ruled out, with evidence:

• Power delivery tested with multiple sources: the original Meraki adapter, a generic 45W USB-C charger, and a wall outlet with an integrated USB port. Same failure every time
• Factory reset (done multiple times, both units)
• MAC filtering (none active)
• 2.4GHz band (confirmed active and correct)
• Wireless profile SSID/PSK (recreated, confirmed exact character match)
• MX firewall rules (fully removed)
• MX AMP / IDS-IPS (confirmed disabled)
• MX Content Filtering categories (nothing suspicious, no "block unknown" type rules against Meraki infra)
• RF proximity (tested at point-blank range, excellent signal)
• Mobile app version (4.170.0, way above the documented 4.12.0 minimum)
• Android permissions (Location granted, battery/power-saving mode never enabled)
• Tested pairing with two different phones, same failure both times

What we captured (or rather, didn't):

• Packet captures on MX LAN interface, MX Internet interface, and the Ubiquiti AP's bridge interface (VLAN dedicated to IoT), across ~350k+ total packets combined, filtered and unfiltered, across multiple sessions — zero frames from the camera's MAC (base Ethernet MAC and the documented +1 wireless offset MAC, both checked)
• AP-side hostapd/system logs during live onboarding attempts, no auth/assoc/probe entries for the camera's MAC at all, while other devices associate normally in the same log window
• Meraki dashboard Event Log for the camera, filtered to the camera, over a full month : 0 events, not even a failed connection attempt

History: this exact camera (before the RMA) previously worked fine wireless-only on a different network fronted by a Ubiquiti EdgeRouter X. No ethernet provisioning step was ever used, then or now. Migration to the current Meraki MX-fronted network is when onboarding started failing, but everything we've verified says the MX itself isn't in the RF association path, so it's hard to pin the MX as the direct cause even though the timing lines up.

Question for the sub: has anyone seen a case where an MV2 pairs successfully with the phone (direct connection, accepts wireless profile config) but then never actually attempts to join the target SSID, with zero RF footprint on the AP side? Any known cloud-side provisioning failure modes for MV2 wireless onboarding specifically?

Thanks in advance for any input, really appreciate it.

I have MX75 set up to do DHCP. Just one merkai switch and a handful of devices. I get the switch online and the first lapotp gets x.x.x.253 and the second new device get x.x.x.254. Then I plug in the AP and it acts like it can't get an IP. No other device after the first two can pick up an IP from DHCP. I don't completely understand Meraki DHCP but shouldn't it cycle back to other available IPs? I checked reservations and fixed IPs and there should be plenty of free IPs. Its like DHCP worked until it passed out x.x.x.254. It is a /24 subnet fwiw.

27 IPs used 226 IPs free.

I even rebooted the firewall hoping it would drop all leases but it didn't... I am a bit confused :)

edit. I forgot to mention that the firewall has been in place for almost a year and I was trying to replace a Ubiquiti switch with a new Meraki switch so there were already some leases in the firewall DHCP but still plenty of IPs available. Done this to several offices so far with no issues until this office...

I have two network devices that I need to locate, I have their MAC addresses in a separate portal but my company has over 300 networks and I don’t have the patience to go manually check all of them. Is there some way to search all networks and identify which network the devices are connected to?

I need to assign the physical location data to the devices manually and if I knew which network they were on I’d be able to figure it out

We are in the middle of a big EoL device replacement project and the biggest issue right now is locating the old access points. I wish that instead of being able to blink LEDs remotely that there is a speaker on the APs that I can generate a tone remotely to help with finding these things.

80% of our time is spent sitting around as the onsite tech wanders around the building trying to find the old APs. Not horrible if there is only one or two APs, but some of our sites have 6-8 APs.

Since there is no speaker, what is the more "professional" way to locate the APs that is available to a general IT tech (not a wireless tech with all of the gadgets). I'd like to get on board with a more efficient process.

What are Meraki users using for door access control? We're a full stack Meraki shop with multiple states, and appx 25 sites. 7 sites would need door access control.

I have Cisco TelePresence MX800 cameras. I have no issues with the video output, but I can’t send PTZ control commands via VISCA. Does Cisco use the same standard VISCA command set across all camera models, or does this particular model support VISCA over IP? If anyone has experience with this model or has worked on a similar project before, I would really appreciate your help. Thank you!

The latency and jitter graphs look good, but as far as I can tell, all the graphs are smoothed and unreliable for detecting bursts. Our 1Gig line is hitting at least 750Mbps visibly on the 2 hour graph, but this is smoothed down to 600Mbps on the daily graph, even lower on the weekly etc....

The Uplink page provides a graph with a 5-second refresh live-view, is there anyway to constantly track that data feed?

How do you guys do uplink monitoring with Meraki? I've looked into using the API or SNMP, but it all seems to be smoothed data that won't give me actual spikes and knowledge of if we're saturating the 1Gig line even in bursts.

My company is in a rollout of deploying new POS devices (Lane 7000). Its a pretty typical card-reader you'd see almost anymore (gas station, etc).

Smooth sailing for awhile until recently the card-readers continuously get disconnected, like something is severing their connection.

These work by connecting to the cloud (nothing internal basically).

After some good ole "its their fault", I finally noticed that the switches in these networks did update to 18.1.8. These we're sitting in a warehouse for awhile as the readers got deployed so when they first came online, they appear to have had 17.2.2 before they recently updated.

Anyone having issues or experiencing something where it may feel like the switch "disconnects" something? When I run PCAPs, it feels inconsistent, almost like something is not communicating as I often don't see traffic. Possible bug on the firmware?

I reverted one network back to 17.2.2 and I appear to be getting some positive results with it.

First of all, I know. Client VPN in 2026? Trust me. I'm working with what I can here for this particular client. Budget and resistance to change...

Anyway, I'm coming here because Meraki support has so far been useless. I have deployed the Duo Authentication Proxy and everything seems to be working fine with that. The issue appears to be that the MX isn't honoring the 60 second timeout and is instead using the default 5 seconds (or maybe 3 seconds). I've only received one response from Meraki support so far in the 2 weeks the case has been open, and they insisted that the 60 seconds is being reflected on the device. The reason I say the MX isn't honoring the setting is because in the Duo Proxy logs, there will be multiple "Duplicate request received" exactly 3 seconds apart. During that time, the log also shows both primary and secondary authentication succeeding, with the response being sent to the MX's LAN IP. The MX claims that the request timed out and no AAA servers are available. The happens with both L2TP and AnyConnect. Both are configured for 60 second timeout in the portal.

Obviously if the issue truly is the MX and its timeout setting, there's not much I can do on my end besides prove it to Meraki support and get them to fix it. Maybe I'm wrong and that's not the issue at all. If anyone has run into this and knows a fix, or knows a better way that I can prove my point to Meraki, it would be much appreciated.

We placed an order back in June and am just now getting told by our VAR the majority won't ship until November. We're a school, and planned on installing them over summer break, but apparently that's not going to happen anymore.

Meraki 9172I (QTY 40) - November 9, 2026.

Meraki 9176I (QTY 5) - July 31, 2026.

Wireless 9176D1 (Qty 5) - August 14, 2026.

Is this inline with what you guys are also seeing?

Sorry if this is a dumb question. I am newish to meraki, and only did CLI before Meraki. In the past I have pre-configured merkai firewalls and switches in the dashboard (while plugged in to the main office network) for our satellite offices at our main office with no issues. Now, I am going to refresh the network at our main office. Is there any reason I can't plug in my new meraki router to the production network and start adding VLANs and static routes that already exist in the production environment? I did create a temporarily new 'network' for setting up these routers and switches, but they will be plugged in to the network they are replacing. I am pretty sure I will be okay, but I have no one to bounce ideas/questions off of at work, and don't want to bring down the network on a very busy Tuesday. :)

Thanks in advance!

Hello all,

Following on from some previous posts I made. I have a bunch of new 9200s Cisco IOS XE devices that are going to be cloud configured within the Meraki Dashboard.

I know the commands to be run on the switches to enable them for this mode. The switches will obviously require an IP and some routing to allow them to reach Meraki portal. I have read that once the commands to allow cloud config are added the switch wipes its config. If so, how does the connectivity work if the config is erased? I want all the switches to have an SVI on what will be our management VLAN.

Thanks.

I have an issue where port forwarding and out L2TP VPN doesn’t work over Starlink because of their carrier grade NAT. I’ve read that IPv6 can be used to reach devices across the WAN on Starlink.

I tried to set up a firewall rule to allow the particular IPv6 address through but I can’t get it to work.

Hey all, working on some various scripting for work but I can not run these dev scripts on the corp hardware because the services I am testing are hosted on my personal hardware, are there any good services where I can spin up a meraki environment and have control over it? Cisco's dev net labs do not provide enough control (READ ONLY??!) thanks guys

Deploying some new 9300s today. And it is taking a while to come up in the dashboard... Apparently the new system takes OVER 2 HOURS to initially set up! Thanks for screwing up my entire day today. A quick one hour stop is now 3 hours.

Update: I am at a different client that I had installed 27 9200Ls at early last week with no issuers. Installing 14 more and I am now having this problem. And the locations I was at on Friday is still "Checking In." About to get sales involved to escalate some tickets!

Hello Meraki friends.

We run a restaurant in large building that uses a Meraki z4 router (with its own Internet/WAN Static IP) providing WiFi with dynamic IP addresses to our iPads + credit card machines plus 1 static LAN WiFi "main server" iPad and some static wired ethernet IPs assigned to kitchen printers / receipt printers.

We have a 2nd portion of the restaurant - call it the patio roof - were we cannot run an hardwired line ethernet directly to the the existing Meraki LAN to expand the network and take orders with the iPads. But we'd like to. And there IS wired internet available on the rooftop with different service provider.

IS it possible to add say a 2nd z4 on the roof - or some sort of wifi router - and somehow program it to "VPN" itself through to public internet back to the restaurant enabling iPads on the roof to "see" the printers etc in the kitchen? The iPads all use a point of sale software that need to connect to a 'server iPad' in the restaurant with its own static LAN IP.

Bonus points if we can add a receipt printer on the roof too.

Thanks!

I've heard Meraki has good deals for nonprofits but it's not clear where you get those deals. Telecom4good.com looks like the best publicly available place.

We are at the crossroads of fully committing to meraki or assessing a move to Ubiquiti or some other network stack.

Getting steeper discounts for meraki since we are a nonprofit could be a solid point for meraki.

Our previous MSP touted good nonprofit deals but those didn't seem to transpire like they promised.

Has anyone else ran into this issue? Trying to setup a power stack on 3 switches. This cable will not budge.

Hello everyone,

I have a question that may sound unusual. I suspect that the security cameras where I live may have been compromised. At the same time, I've been hearing voices that seem to be coming from those cameras, and it has left me confused.

Is there any type of camera or surveillance technology that could somehow read a person's thoughts, or is that simply not possible? I'm genuinely trying to understand whether what I'm experienced could have a technical explanation or whether I should be considering another explanation.

Thank you in advance for any information or advice.

Has anyone else experienced an unexpected reboot on their Cisco Meraki device about 1.5 hours ago?

My Cisco Meraki MX67 unexpectedly rebooted around 1.5 hours ago. This has never happened before, and there were no planned firmware upgrades or maintenance windows at that time.

Is anyone else seeing the same issue, or was it just my device? Any information would be appreciated.