Meraki

alemabrahao

Force Domain Controllers to use ONLY the Umbrella for DNS and block all outbound traffic from Domain Controllers except HTTPS and any internal networks.

alemabrahao

It depends, in some cases it's not necessary. Take a look at this article. SFP vs SFP+: A Complete Guide to Compatibility and SFP+ Modules

alemabrahao

It's not necessary.

alemabrahao

A Cisco Smart Account is basically an online central repository where your company stores and manages all Cisco software licenses, subscriptions, and entitlements. Cisco is transitioning more licensing workflows to Smart Licensing, and now all license-enabled product orders need to be assigned to a Smart Account before they are fully processed. Meraki uses its own Dashboard Organization-based licensing system, completely separate from Cisco Enterprise's Smart Licensing. https://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/smart-software-manager-satellite/at-a-glance-c45-734361.pdf

alemabrahao

The MX cannot operate as a compatible edge BGP router with your ISR. It only performs simplified eBGP, geared towards AutoVPN.

alemabrahao

alemabrahao

Licensing devices in Meraki MDM requires adding SM licenses to your organization via Organization > License info and ensuring you have available licenses to cover the device count. Once licensed, enroll Android devices using Systems Manager > Manage > Add devices https://documentation.meraki.com/Platform_Management/Product_Information/Licensing/Systems_Manager_Licensing#:~:text=LIC%2DSME%2D1YR-,Exceeding%20SM%20Licenses,is%20available%20and%20in%20compliance.

alemabrahao

Just a reminder. Effective June 3, 2026, Cisco Meraki Systems Manager will be discontinued and no longer available for purchase. In accordance with Cisco’s product lifecycle policy, existing customers will continue to receive technical support and maintenance updates through the Last Day of Support. For details on support timelines and recommended alternatives, please refer to the End-of-Sale FAQ

alemabrahao

It should work if you use BGP. https://documentation.meraki.com/SASE_and_SD-WAN/MX/Design_and_Configure/Configuration_Guides/Site-to-site_VPN/BGP_routing_over_IPsec_VPN

alemabrahao

The 20-minute interval is fixed; you cannot change it.

alemabrahao

Systems Manager does not currently support displaying the device name directly on the Android/iOS Kiosk Mode screen.

alemabrahao

Conducting a site survey is key. 😉

alemabrahao

There is no way to delete a SAML user from Meraki’s backend. Only a SAML reset clears it. Solved: SAML SSO - user/email address removal - The Meraki Community

alemabrahao

You don't need to configure one port at a time; you can select multiple ports and configure them as desired. https://documentation.meraki.com/Switching/MS_-_Switches/Design_and_Configure/Configuration_Guides/Port_and_VLAN_Configuration/Configuring_Multiple_Switch_Ports_on_the_Same_VLAN

alemabrahao

There is no way to change the Calling-Station-Id in the L2TP/IPsec Client VPN. The recommendation is to migrate to AnyConnect, which sends more useful information and does not use "CLIENTVPN".

alemabrahao

Take a look at this. Solved: Modify the Client VPN's CallingStationId to the Client's IP - The Meraki Community

alemabrahao

Meraki's official rate limits today are 10 requests/second per organization, with an additional +10 in the first second (token-bucket), shared by all applications using that organization's API budget, and 100 requests/second per originating IP. Rate Limit - Meraki Dashboard API v1 - Cisco Meraki Developer Hub

alemabrahao

You can schedule it. https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/Monitoring_and_Reporting/Summary_Report_Overview#Emailing_and_Scheduling_Reports

alemabrahao

When the spare comes online: it downloads the same configuration as the primary (as required for Warm Spare) it establishes VRRP heartbeats with the primary it synchronizes required HA state (DHCP leases, monitoring, etc.) it transitions into the Spare/Passive role while the primary remains Primary/Active Only now is the Warm Spare pair fully operational. Remember that both MXes must be the same version. The documentation provides all the additional details.

alemabrahao

Remember that this is the behavior of VRRP, which is an open protocol and can be implemented by any other vendor. https://www.haproxy.com/glossary/what-is-vrrp-virtual-router-redundancy-protocol

alemabrahao

That's not what I meant. Simply adding the MX to the inventory (dashboard) doesn't cause a problem; adding it to the network does, and that's the expected behavior due to what I explained in the first post. Ideally, you should do this during a maintenance window, as you need to make all the connections so that the MXs can exchange VRRP information. Meraki documentation explicitly states that Warm Spare requires two online MX units configured for VRRP-based HA to operate. Warm Spare logic starts ONLY after the secondary MX is powered on, connects, and establishes VRRP communication with the primary.

alemabrahao

Warm Spare logic only becomes active once BOTH MX units are online and connected, not simply when the second MX is added to the Dashboard network.

alemabrahao

https://documentation.meraki.com/SASE_and_SD-WAN/MX/Design_and_Configure/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair Take a look at the documentation for more details.

alemabrahao

A brief service disruption is expected when converting a standalone MX into a Warm Spare pair, and it is caused by how Meraki MX handles VRRP activation, shared IP assignment, routing roles, ARP re‑learning, and network topology updates, not because the MX should go down, but because the network must transition from a single-router architecture to a redundant VRRP-based architecture.

alemabrahao

What is the model of your Meraki device? I've never heard of or seen anything similar.

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges