I've used Fortinet SFPs before and they worked without any problems. ... View more

Okay, just to confirm, you're using Meraki APs, right? You need to enable everything related to the Unifi Portal on Walled Gerden. Also, try disabling the device's random MAC address.   https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Walled_Garden ... View more

macOS has aggressive DNS caching and sometimes prioritizes certain interfaces or DNS servers based on perceived latency. If the Cisco Secure Access Client is enforcing DNS policies (e.g., tunneling DNS), macOS may still try to resolve via the Wi-Fi interface first, leading to delays or failures if there's packet loss or latency spikes.   Even if DNS servers are reachable, the client may enforce DNS routing through the VPN tunnel. If latency spikes cause packet loss or delay, DNS queries may timeout before falling back to local resolution.   You can try temporarily disabling DNS tunneling in the Secure Client profile and see if DNS resolution improves over Wi-Fi. ... View more

For now it remains unsupported, hoping it will be supported soon. ... View more

The Meraki MA-ANT-27 is a great choice for a 200 ft directional shot to cover a couple of booths in a parking lot. meraki.cisco.com/product-collateral/dual-band-sector-antenna-datasheet/?file ... View more

@RaphaelL wrote: Hi ,   I'm facing a weird situation 100% caused by bad inventory management on our end. We bought thousands of MX68 couple years ago , stocked them in a warehouse and slowly deploying them. We are now at a stage that some MXs have NEVER been deployed after couple years and obviously are running an old 2018 firmware.   That old version ( 14.xx ) CANNOT upgrade to 19.X or 18.X without going to 16.X. If you simply upgrade from 14.XX to 19.XX it will reboot in loop and fail the upgrade every time ( without letting you know that the upgrade cannot complete 💔 ).   Opened a case , support suggested creating a dummy network with version 16.16 and doing that firmware upgrade process :  14.34 -> 16.16 -> 18.107.5 -> 19.1.9   You cannot add more than 1 MX per network and I have hundreds to upgrade. We don't know the firmware on the boxes so, we can't really take a chance and ship a MX to a site and expect ZTP not to fail.   If only the dashboard could check the firmware version and do that step upgrade process by itself 😉     I don't see any easy solution. Every option is time consuming. To be honest, I don't see an easy solution for your situation. What I would do in your position would be: Create a dummy network with firmware 16.16 (which I don't think is possible). Add one MX at a time, upgrade it through the steps. Then move it to production. ... View more

Cisco support can help ensure licenses are applied correctly and old devices don’t interfere. ... View more

Is Energy Efficient Ethernet enabled?   https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Energy_Efficient_Ethernet ... View more

Note: When connecting a PVST+ bridge to an MS series switch, make sure both ports are configured as an 802.1Q trunk. Otherwise, the PVST+ bridge will go into a blocking state due to port inconsistency. To avoid any issues with STP, it is recommended to convert the Cisco Catalyst environment to single instance MSTP. This will ensure maximum compatibility in the STP environment.   https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Configuring_Spanning_Tree_on_Meraki_Switches_(MS)#MSTP_(802.1s) ... View more

Modern Windows systems may send DNS queries simultaneously via both VPN and LAN interfaces, using the fastest response. This can cause unpredictable behavior, especially over Wi-Fi.   If the Secure Client is configured to tunnel all DNS traffic, it may bypass local DNS resolution, causing failures when the VPN DNS server is slow or unreachable.   Cisco Secure Connect - DNS Troubleshooting - Cisco Meraki Documentation ... View more

Your answer is here.  It is not recommended anymore.     IMPORTANT: Notice on API requests to undocumented base URIs - The Meraki Community ... View more

It's like I told you, there you have an overview, for example, OSPF and BGP are within L3 Switching. So you would need to go into the guide for these features to validate the minimum requirements. I'm not sure if that's clear?   https://documentation.meraki.com/MS/Layer_3_Switching/MS_Layer_3_Switching_and_Routing https://documentation.meraki.com/MS/Layer_3_Switching/MS_OSPF_Overview ... View more

In this case, you cannot whitelist the IP in IDS/IPS directly, but you can allow the traffic using Layer 3 firewall rules and adjust IPS settings to avoid blocking the scans. ... View more

Meraki MX does not support direct port scanning of LAN subnets from external (WAN) sources unless you configure port forwarding or NAT rules to expose internal devices. Even then, only the public IP of the MX is exposed, and internal devices are not directly reachable unless explicitly configured.   MX Firewall Settings - Cisco Meraki Documentation ... View more

Here's the list of features supported by each licensing model. It's a bit complicated because not everything supported by the traditional Catalyst line is supported by Meraki. Therefore, the licensing level won't give you a complete picture of what's supported and what's not.   https://documentation.meraki.com/General_Administration/Licensing/Subscription_-_MS_Licensing   https://documentation.meraki.com/MS ... View more

I use it in most deployments, especially when it comes to Wi-Fi. In general, it works very well for me, both for Wi-Fi and MX. When I encounter some kind of limitation, I prefer to leave it out of the template. What exactly are you having trouble with besides the Meraki App OS issue? ... View more

To simulate it, no, you can use Cisco dCloud. It's not exactly a simulation, but it helps in some cases.   https://content.ciscodcloud.com/content/cisco-dcloud/us/en/home.html ... View more

I suggest you open a support case. ... View more

Note: Layer 3 firewall rules are stateless when configured within Meraki Dashboard group policies. Group policy layer 3 firewall rules can be based on protocol, destination IP (or FQDN for MX and Z-series appliances), and port. You can specify a range of ports, such as "1024-400" in group policy layer 3 firewall rules. However, listing individual ports separated by commas, such as "80,443" is not supported.     https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Using_Layer_3_Firewall_Rules     You need to create two rules, one specifying port 1433 as the destination and the other as the source.   ... View more

As mentioned by @RWelch, yes and you need to version 17.18.1 ... View more

You can try this one organizations/{organizationId}/devices/availabilities/changeHistory ... View more

I suspected it from the beginning. 😅 ... View more

Hi @Phi-L    But the release notes for the most current version and the release candidate version state the following:   Legacy products notice When configured for this version, MX64(W), MX65(W), MX84, MX100, and vMX100 devices will run MX 18.107.13. ... View more

From what I saw, this version is still a candidate for stable, and there are some considerations.   Before you upgrade or migrate: key considerations After migrating CLI/DNA managed switches to cloud configuration source, please note that console and SSH access are no longer available. All management access is only available via the cloud Dashboard or the local status page through the rear management port. Please refer to the documentation (https://documentation.meraki.com/MS/Cloud-Native_IOS_XE/Cloud-Native_IOS_XE_Overview#Changes_in_Behavior) to familiarize yourself with management interface architecture changes. Layer 3 switches cannot run DHCP servers on uplink interfaces with IOS XE 17.15+. Post-upgrade, Interfaces with both Preferred Uplink and DHCP server configurations will have the DHCP server configuration disabled on that interface. Switches using the Alternative Management Interface (AMI) will require an L3 SVI to be configured for the same VLAN assigned to AMI. For AMI to work, your network must have AMI configured and your switch must have an SVI configured matching that AMI VLAN. After upgrading from CS to Cloud Management with IOS XE firmware, port mirroring configurations on module ports will not be retained. Users will need to reconfigure port mirroring on module ports following the upgrade. The 30-day grace period applies to licensing for Catalyst switches onboarded to Meraki Dashboard, allowing customers to trial cloud mode prior to fully committing. Valid DNA licenses can be converted to Meraki licenses through a qualified promotion process. Refer http://cs.co/9005aw6VH for more details.     If I were you, I would downgrade to the stable version (CS 17.2.2) and wait until iOS XE 17.15.4 becomes stable or wait for a new version. I also suggest you open a support case. ... View more