Yes, you do, as switches managed via Meraki Cloud do not support mode on. ... View more

Have you tried creating a traffic shaping rule for Webex?   https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Traffic_and_Bandwidth_Shaping ... View more

Meraki only supports LACP for link aggregation, It does not support static (mode on) EtherChannels. You must change the EtherChannel configuration on the Cisco 3750 side from mode on to mode active.     You can do link aggregation in Merki on different switches in the stack without any problem.   ... View more

I don't think so, the page is meant to give you an overview. ... View more

I don't see why you can't do this in the template; worst case scenario, you can just roll back. Just do it during a scheduled maintenance window so you can perform the activity without any problems. ... View more

HI,   Selective Wipe and Device Quarantine in Systems Manager - Cisco Meraki Documentation ... View more

Wrap your rules in a tolist() to force Terraform to treat it as an ordered list. ... View more

Take a look at this.     https://documentation.meraki.com/MX/Site-to-site_VPN/BGP_routing_over_IPsec_VPN ... View more

In this scenario, the ideal would be to have a vMX on AWS to use Meraki's SD-WAN, Meraki's Ipsec VPN is very limited.   https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings   https://documentation.meraki.com/MX/MX_Installation_Guides/vMX_Setup_Guide_for_Amazon_Web_Services_%28AWS%29   ... View more

Mloraditch,s statement is true. ... View more

You can try using a script (e.g., Python or Bash) that calls the Meraki API directly in the desired order. Terraform can trigger this script using the null_resource provisioner and local-exec. ... View more

Yes, you can, just add it to your inventory and then add the AP to the desired network.   https://documentation.meraki.com/General_Administration/Inventory_and_Devices/Using_the_Organization_Inventory   https://documentation.meraki.com/General_Administration/Inventory_and_Devices/Adding_and_Removing_Devices_from_Dashboard_Networks#For_MR.2C_MS.2C_MC.2C_MV.2C_MT.2C_and.2For_MG_series.2C_as_well_as_legacy_products: ... View more

To manually configure WAN 1 and WAN 2 as primary and secondary on a Meraki MX67 (or similar models), you can use Load Balancing and Flow Preferences in the Meraki Dashboard.   MX Load Balancing and Flow Preferences - Cisco Meraki Documentation   Disable Load Balancing if you want strict primary/secondary behavior.     ... View more

The Meraki Client VPN (using L2TP/IPsec) has a recommended limit of 500 concurrent users. This 500-user limit is specific to Meraki's native client VPN implementation, not necessarily for third-party VPN clients like the Microsoft Native VPN Client. This doesn't mean it won't accept more connections; it's simply a number that ensures the MX hardware won't work beyond its designed capacity. ... View more

Preamble puncturing is allowed only in channel widths greater than 80 MHz.  It’s not supported for 40 MHz channel width.   https://documentation.meraki.com/MR/Wi-Fi_Basics_and_Best_Practices/Wi-Fi_7_%28802.11be%29_Technical_Guide#Preamble_Puncturing ... View more

Thank you guys and congratulations @Mloraditch  ... View more

Do you have the full S/N? If so, you can check it on the Cisco website.   https://cway.cisco.com/mydevices/devices   Take a look at this list.   https://github.com/panoramicdata/Meraki.Api/blob/main/Meraki.Api/MerakiClient_SerialNumberInfo.cs ... View more

Good luck on your journey.   https://meraki.cisco.com/product-collateral/meraki-campus-deployment-guide/?file   https://documentation.meraki.com/Architectures_and_Best_Practices/Recommended_Topologies/MX_and_MS_Basic_Recommended_Layer_3_Topology   https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/General_MX_Best_Practices   https://documentation.meraki.com/MS/Deployment_Guides/Advanced_MS_Setup_Guide   ... View more

Most people assume that clients always connect to the nearest (strongest) AP. But it is the client device, not the AP, that decides which AP to associate with.   Clients base this decision on a variety of factors, including: Signal strength (RSSI) — usually the most important factor, but not the only one. Signal-to-noise ratio (SNR). Data rates supported. AP load (some clients support 802.11k/v/r and may try to avoid congested APs). Roaming algorithms coded by the device vendor (different drivers behave differently; for example, iPhones roam more aggressively than some Windows laptops). Some devices "stick" to an AP even as they move away until they fully disconnect. ... View more

It doesn't matter, both will work. ... View more

Unfortunately, no, there is no field in the API that displays "last login" or "last association date" for merakiAuthUsers. The only dates you get are "createdAt" and "expiresAt" (if set; in your example, it says "Never"). Therefore, you can't determine the last activity directly through the current Meraki API. You can check client association events in the dashboard (through the Events API or Syslog), but the Meraki Events API doesn't currently provide a "last access" date per user account, only per device (client MAC).   And yes, you can automate it, but since there's no "last login" field, you'll have to rely on createdAt or some external data source, and you'll obviously need to schedule it to run on a system, like a Linux crontab. ... View more