https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_

Design/Best_Practice_Design_-_MR_Wireless/High_Density_Wi-Fi_Deployments

Configuring a syslog server for the network is the Cisco Meraki best practice method to preserve

complete historical network event logs. A syslog server can be configured to store messages for

reporting purposes from MX Security Appliances, MR Access Points, and MS switches1. The syslog

server can collect various types of events, such as VPN connectivity, uplink connectivity, DHCP leases,

firewall rules, IDS alerts, and security events2. The syslog server can also help with troubleshooting

and monitoring the network performance and security.

Route Priority

Each type of route configured on the MX has a specific priority in comparison with other types of

routes. The priority is as follows:

Directly Connected

Client VPN

Static Routes

AutoVPN Routes

Non-Meraki VPN Peers

BGP learned Routes

NAT*

https://documentation.meraki.com/MX/Networks_and_Routing/MX_Routing_Behavior

Thank you for your visit.

This can be determined by looking at the concentrator routing table and finding the entry for the

destination IP 10.116.32.4. The next hop for this entry is the Auto VPN peer “Store 1532 – appliance”.

This question is related to the topic of Implementing Dynamic Routing Protocols in the Engineering

Cisco Meraki Solutions (ECMS) official training documentation. You can find more information about

this topic in the ECMS v2.2 Course Overview or the ECMS1 v2.1 Course Overview.

Before deploying MXs as one-arm VPN concentrators, place them into Passthrough or VPN

Concentrator mode on the Addressing and VLANs page. In one-armed VPN concentrator mode, the

units in the pair are connected to the network "only" via their respective ‘Internet’ ports. Make sure

they are NOT connected directly via their LAN ports. Each MX must be within the same IP subnet and

able to communicate with each other, as well as with the Meraki dashboard. Only VPN traffic is

routed to the MX, and both ingress and egress packets are sent through the same interface.

https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_

Design/Best_Practice_Design_-_MX_Security_and_SD-

WAN/Meraki_Auto_VPN_General_Best_Practices