I've removed all my config and disabled it to be safe as I don't want hidden config being left behind! ... View more

See this topic, might be a 17.2.1.1 issue. OP on this fixed their issue with upgrade to 17.2.2   https://community.meraki.com/t5/Switching/Problems-with-printer-after-upgrade-MS-Switches-225-to-latest/m-p/276928#M21109 ... View more

Yes performance numbers much less than expected especially for being a hub for an SD-WAN solution. Also the list price at $42,000 is a lot more than the $30,000 I was told to expect this summer. ... View more

Configuration error. 😄 ... View more

I enabled it via Early Access, but I'm not able to fill the energy prices in the Network so I also requested access for the Beta. This is very interesting from a sustainability perspective. ... View more

Personally I can't imagine myself staying on the CS train. Disregarding a few dashboard features that are not yet available on 17.15.3.1 or beyond you get better insight into potential issues where you actually need some CLI output to verify.   Dashboard is great for checking endpoints, but checking the device operation is way better if you have cli access. Having said that, nobody is pushing yet to move away from the CS train. ... View more

I've always used either the SFP(+/28) ports or port 1 for uplinks, no idea why, but it looks like a good plan now 😂  ... View more

Sorry about that last sentence. I meant disabled, not enabled. 😉 I've been doing that for months. I also just noticed that since yesterday, the link for cookie settings is at the bottom right and no longer opens. Let's see if it's just another temporary bug. ... View more

I think the last time I looked at this (years ago) we didn't quality for access to the API. I will have another look and see if that has changed. Thank you! ... View more

No, actual Ethernet (copper) port. these are used for data center mostly but we use them for SAN connection between VMWare/Hyper-V and SAN storage. 9300 series are good for campus in access layer. they can't handle SAN traffic.   ... View more

Just wanted to feedback to everyone here. We never found the exact issue, however, we suspect it to have something to do with setup procedure. We eventually just did everything from scratch. Deleted the API key, removed the syslog entries, and deleted the Forescout config. (When we originally started this, we created the API key, and loaded it onto Forescout where it registered. Only then did we change syslog details on the Meraki network.) Then did it all again. New API key, syslog config and Forescout Meraki plugin load and config. This time, we created the API key, configured the syslog events on Meraki network and only then loaded the API key on Forescout (once all the Meraki setup steps were done) I can't imagine how the procedure would make a difference, but at least worth noting the steps I guess. We are now facing a 10 min window, instead of 12 hours like before. VAST improvement. Still not near instant as when using postman, but much better. We will be playing with timers on Forescout to see if this can be improved as well. If we manage to improve this, I'll feedback here. Almost wish we can reproduce the 12 hour issue now to find the actual problem... ... View more

Agreed — Meraki’s RBAC model needs to evolve. I’d like to echo the point about outgrowing the current Admin vs. Read-only roles. For organizations with tiered support (Tier 1–4), the lack of granular access controls creates operational and security challenges — especially when using SSO. Solutions like Boundless Digital offer the kind of role-based granularity that’s becoming essential. The real challenge is maintaining the “Meraki Simple” experience while expanding access control flexibility. Would love to see Meraki explore native enhancements that strike this balance — perhaps starting with customizable permission sets tied to SSO roles. ... View more

It turned out to be a bug in the Cisco OS, we reloaded the Cisco switch and traffic is passed again. Looks to be a layer 2 issue.    Version 17.09.04a ... View more

It is normal for devices to roam between APs.  Why is that an issue?   Some things to check: Is the SSID in bridge mode?  NAT mode will cause issues for a phone. Check out this post I did about enabling AI channel planning: https://community.meraki.com/t5/Wireless/Link-negotiation/m-p/276864/highlight/true#M38339 Have you created a wireless profile?  I mostly use the "Open Office Profile". https://community.meraki.com/t5/Wireless/Link-negotiation/m-p/276875/highlight/true#M38342 ... View more

Hi Raphael  This is a known issue that is resolved in firmware version MR 31.1.6 (Stable release candidate). Please upgrade the devices and let me know if the issue still occurs.   I just wished ( real bad ) that MR firmware would include more fixes instead of "General fixes and improvement". This would prevent me from opening a ton of cases.    Will try that firmware and report ... View more

If you need detailed information about the MTBF, I think you'll need to reach out to your Meraki AM or open a case with Meraki Support. ... View more

Hi @pokemaster. This thread is about an upgrade we are doing to Meraki Cloud Infrastructure as part of Meraki Cloud Infrastructure PCI compliance which is different than PCI compliance of a Meraki network on the customer side. Please open a Meraki Support case for us to look into that for you. ... View more

PXE boot across the WAN? Is that a thing? ... View more

If migrating the site to Meraki, in order to leverage AutoVPN isn't an option, you could use an MX as a termination point of the Non-Meraki VPN, and route that, statically or dynamically, into the rest of your Meraki topology. It would require you to buy another MX and create a "Gateway" network, which function as the entry point between AutoVPN and Non-Meraki VPN.  ... View more

You will likely need to engage Meraki Support. in order to convert the switch from Cloud Configuration to Device Configuration ( => Meraki to Catalyst). ... View more

for the settings on the Meraki CW9164 access point I have done it to be able to support the 6GHz frequency and I have consulted with the distributor where the 6GHz band support is not yet available in the latest firmware on Cisco Meraki wireless, as for the new frequency that can only be activated on Cisco Catalyst non Meraki, and I have opened an issue ticket in Meraki support with the same answer that it cannot be activated in Indonesia while the regulations are clear that devices that have a 6GHz band and even Wi-Fi 7 can already be used. Hopefully this hope can be realized from Cisco Meraki internally, considering that our devices cannot be fully maximized ... View more

Yes, this is supported regardless of the model. https://community.cisco.com/t5/security-knowledge-base/how-to-integrate-meraki-networks-with-ise/ta-p/3618650#toc-hId-1281948796 ... View more

🤣 ... View more

We’ve experienced the same issue after upgrading our switches to 18.1.2. Wireless clients connected were not receiving DHCP addresses. Once we rolled back to 17.2.2, everything returned to normal.   For context, SecurePort is enabled in our environment, and we confirmed the problem was isolated to MS130 switches only. Other switch families (MS225/MS250/MS425) didn’t show the same behavior, or at least weren’t affected in our case, as only four of our sites upgraded and we primarily use the MS130 range.   We’ve logged a case with Meraki Support so they can investigate further, as this seems consistent with the regression others have described here. ... View more

https://community.meraki.com/t5/Feature-Announcements/Credit-Hub-Unlock-IoT-Outcomes-with-Meraki-Advanced-Wireless/ba-p/283920 ... View more