Meraki

alemabrahao

I usually prefix reconfigure the protchennel and then move the connections.

alemabrahao

So create a separate template and move the networks to this new template, it will be much less work. 😉

alemabrahao

It's best to power on the Meraki switches first. For Cisco switches, it's best to move the connections simultaneously. So, the best option is to run it during a maintenance window, disconnect the connections, access the switch via the CLI (console), change the portChannel configuration, and then move the connections to the Meraki switch. Run all the tests and then move to the new switch. There's no shortcut; just run one at a time and everything will be fine.

alemabrahao

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

alemabrahao

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

alemabrahao

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.

alemabrahao

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

alemabrahao

Take a look at this. https://documentation.meraki.com/General_Administration/Templates_and_Config_Sync/Managing_Multiple_Networks_with_Configuration_Templates

alemabrahao

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.

alemabrahao

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

alemabrahao

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

alemabrahao

Meraki SM supports SAML-based authentication (e.g., Okta, Azure AD, OneLogin) for device enrollment. This can be used to authenticate users during the ADE process if configured properly. Note: If enrollment authentication settings change, iOS and macOS devices enrolling through ADE (formerly DEP) may encounter enrollment issues. Resolve ADE enrollment issues by creating a new ADE payload ensuring the "Use network's user authentication" value is set correctly. SM Enrollment Authentication - Cisco Meraki Documentation

alemabrahao

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

alemabrahao

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

alemabrahao

Mloraditch,s statement is true.

alemabrahao

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.

alemabrahao

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:

alemabrahao

Take a look ate the documentation. https://documentation.meraki.com/MX/Other_Topics/MX_Cold_Swap_Replacing_an_Existing_MX_with_a_Different_MX

alemabrahao

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.

alemabrahao

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.

alemabrahao

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

alemabrahao

It's for a Catalyst 9800, not a Meraki cloud.

alemabrahao

Thank you guys and congratulations @Mloraditch

alemabrahao

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

alemabrahao

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

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges