BRKMER-1005   Solutions - Cisco Zero Trust Architecture Guide - Cisco   Cisco Meraki Free Trial Request Form | Cisco Meraki ... View more

Is the AP port in trunk mode?   Have you checked for any DHCP conflicts?   If I understand correctly, the 9300 is playing the role of the correct core?   Can you share the SVI and DHCP configurations? ... View more

  Not natively. Take a look at splash access.   https://marketplace.cisco.com/en-US/apps/380853/splash-access ... View more

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

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Blocking_and_Allowing_Clients ... View more

But one test you can do is try opening a page manually to see if the splash page loads.     Block Applies the following settings to a client:   Firewall rule applied to block all communication with other devices on the Network (only applies to traffic that traverses the Cisco Meraki device that has the block is configured) Blocked Splash Page will be displayed when user tries to load a web page ... View more

When you block a device, no access to your network is allowed. This includes the splash page, so it's completely expected.   For this to work, you need to set the policy to normal. ... View more

How about deny local lan setting?   https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/%27Deny_Local_LAN%27_settings_in_Cisco_Meraki_MR_firewall ... View more

I understand that you don't want to do this via script, as you'll have to make adjustments from client to client, but this might help.   I personally like to configure the settings manually, as this avoids carrying over settings that aren't in use.   Another detail you need to consider is that not all Catalyst settings exist in Meraki, so you'll eventually have to configure something manually. ... View more

Have you already checked this?   https://github.com/fadysharobeem/Catalyst_to_Meraki_Migration_tool ... View more

Yes, but in some cases it's no longer working. So what leads us to believe that it will stop working anyway. ... View more

Yes, that is right. ... View more

I don't think that's the purpose of Cisco Spaces. ... View more

The cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers module does not support creating new VPN peers from scratch. It only supports updating the entire list of third-party VPN peers for an organization.     cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers module – Resource module for organizations _appliance _vpn _third _party _vpnpeers — Ansible Community Documentation     To use this module successfully, you must First retrieve the current list of VPN peers using the cisco.meraki.organizations_appliance_vpn_third_party_vpnpeers_info module. Them append your new peer to that list, and use the update module to push the full list (including the new peer) back to Meraki. ... View more

Meraki does not currently expose detailed module-level inventory via the API.     You can Get Only Active/Available Ports (Including Uplink Modules) using this API.   Get Device Switch Port - Meraki Dashboard API v1 - Cisco Meraki Developer Hub   And for General Device Info you can use this one.   https://developer.cisco.com/meraki/api-v1/get-organization-inventory-devices/ ... View more

You can create Group Policies in the Meraki Dashboard and assign them to specific VLANs.   These policies can include, Traffic shaping rules, Bandwidth limits and Application prioritization. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies ... View more

You weren't really clear, because I checked the 9800 datasheet. But in your case, keeping it off Meraki and using Catalyst Center is a more viable option, in my opinion. Especially because the C9800 has more features. And another thing is that I don't see the point in adding a Wi-Fi controller to the Meraki dashboard, since Meraki already has its own Wi-Fi solution. So why spend money on a controller if you can just buy the APs? ... View more

This is how it was designed, if you want a larger number of supported APs you need a "larger" controller, that is, with more features to be able to support a larger number of APs/Clients. ... View more

Take a look at the documentation.   https://documentation.meraki.com/MS/Layer_3_Switching/MS_Layer_3_Switching_and_Routing ... View more

When you changed the native VLAN to a "trash/unrouted" VLAN, the switch port may no longer be tagging the management VLAN traffic correctly. If the management VLAN is not explicitly tagged on the trunk, and the native VLAN is no longer the management VLAN, the switch might not be able to reach the Meraki cloud using its static IP. Them Meraki devices will fall back to DHCP if they can’t reach the cloud with their static IP. This is likely why you’re seeing a random IP from another VLAN, it’s trying to get online via any available path. ... View more

You can try Location Heatmap.   https://documentation.meraki.com/MR/Monitoring_and_Reporting/Location_Analytics#Location_Heatmaps   ... View more

Take a look at this document.     https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Wireless_Client_Isolation   It's under Wireless > Configure > Firewall & traffic shaping   ... View more

The health checks for tunnel monitoring do work in Routed mode, not just in Passthrough mode. The health check probe is sourced from the MX's WAN interface, even in Routed mode. ... View more