When configuring hubs for a spoke, there is an option to select a hub as a Default route. If this option is selected, then that hub will be configured as a default route for the spoke (0.0.0.0/0). Any traffic that is not sent to a configured VPN peer network, a static route or local network will be sent to the default route. This routing will apply to any traffic originating from subnets set to, "In VPN" or that have VPN mode "Enabled." Subnets that have VPN mode "Disabled" will not adhere to the VPN routing tables. Multiple hubs can be selected as default routes. Hubs marked as default routes take priority in descending order (first priority at the top). https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings
... View more
Try adding the route manually on your Windows computer. https://documentation.meraki.com/MX/Client_VPN/Configuring_Split_Tunnel_Client_VPN
... View more
Yes, but the question is, is this hub declared as a hub for this spoke? Packet capture will tell you where the traffic is stopping. Also, have you validated the Spoke's routing table to see if it's actually receiving this route?
... View more
You can find all documentation on the Marki website. https://documentation.meraki.com/MX https://documentation.meraki.com/MX/Networks_and_Routing/MX_Addressing_and_VLANs https://documentation.meraki.com/MS/Layer_3_Switching/Configuring_ACLs
... View more
Security appliance firmware versions MX 19.1.8 changelog Important notice As of MX 19.1, Cisco Meraki will no longer support USB-based Cellular Failover on the MX and Z platforms. New MX 19.1.8 stable release candidate: more fixes than Bob the builder - The Meraki Community
... View more
USB modems with MX/Z series devices running firmware MX 18 or newer will be limited to best effort support and will not be receiving any future firmware fixes or improvements. https://documentation.meraki.com/MX/Cellular/3G%2F%2F4G_Cellular_Failover_with_USB_Modems
... View more
In real life, what you need to consider is your device's memory and CPU capacity. I remember reading that you need about 1 GB of RAM for every 750,000 routes. So, even if you have, say, 128 MB (that's an example) by default, it's best to limit the maximum to 3,000 routes.
... View more
As far as I know, this change can only be made through the Meraki Dashboard. Locate the device in the Meraki Dashboard, remove it from the network, and finally remove it from your inventory. Once this process is complete, you can reactivate the device. If it doesn't work, I suggest you contact Meraki support.
... View more
If you configure port descriptions on Meraki switches, you can use ISE's CoA policies to tag or log those descriptions, but this is limited.
... View more
The NAS-Port attribute (AVP: t=NAS-Port(5) l=6 val=14) does contain the port number, but it's a numeric value that represents the port index or ID as seen by the NAS (in this case, the Meraki switch). Cisco ISE does not automatically map this numeric value to a human-readable port name (like Gig1/0/14) unless the NAS (Meraki) provides additional context. Meraki switches do not send full interface names in standard RADIUS attributes like Cisco switches do.
... View more
Avoid using subnet objects for Meraki devices with DHCP IPs, instead, manually add each Meraki device in ISE with its hostname and MAC address.
... View more
You need to import Meraki-specific RADIUS Vendor Specific Attributes into Cisco ISE. VENDOR Meraki 29671 BEGIN-VENDOR Meraki ATTRIBUTE Meraki-Device-Name 1 string BOTH ATTRIBUTE Meraki-Network-Name 2 string BOTH ATTRIBUTE Meraki-Ap-Name 3 string BOTH ATTRIBUTE Meraki-Ap-Tags 4 string BOTH END-VENDOR Meraki Tuning the Cisco ISE for Meraki Networks – Karstens Cyber-Fi Blog
... View more
Take a look at this document. https://community.cisco.com/t5/security-knowledge-base/how-to-integrate-meraki-networks-with-ise/ta-p/3618650
... View more
If you're hosting your own homepage or using Meraki's custom homepage feature, you can try adding a simple checkbox and JavaScript to toggle password visibility. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Customizing_the_Splash_Page
... View more
I once read (but couldn't find the document) that the MX100 is known to reliably support around 5,000 to 10,000 routes, but performance degradation or route drops may occur beyond that, especially in hub-and-spoke topologies with many spokes advertising multiple subnets. But the truth is that there is no official document that attests to this.
... View more
If the IP settings already exist, Meraki may reject the update. Use the devices_appliance_uplinks_settings_info module to fetch current settings before applying changes. Try changing state: present to state: replaced to force an update. Remove optional fields like pppoe and vlanTagging unless they are explicitly needed.
... View more
That's right, by default the MX will establish the tunnel with the primary WAN. The document is correct. On the other hand. With MX 19.1.4, Meraki introduced official support for failover and failback between non-Meraki VPN tunnels. Configure Secure Access with Meraki MX for High Availability and Health Monitoring
... View more
