Meraki MX — read Auto VPN in the Dashboard view
- WAN & MPLS
- Intermediate
- 15 min
- 4 steps
- Cisco IOS-style
- cisco-meraki
Three Meraki MX appliances form one Auto VPN: a hub (HUB) and two branches (BR1, BR2). One of BR1's subnets is not in the VPN. Meraki has no CLI, so you read the netverdict Dashboard view, predict which hosts reach each other, and check your predictions with ping from the hosts.
Open this lab in your browser →
Free · no install · no account
Scenario
A Meraki MX is configured in the Meraki Dashboard, not on a command line. In netverdict an MX's configuration is its Dashboard document (JSON, as the Dashboard API returns it), and its terminal is a read-only Dashboard view: show vlans, show vpn status, show route, show firewall, show uplinks, show ports. Typing a configuration command there is refused with the reason. Type help for the list. Auto VPN builds the site-to-site tunnels for you. On each MX you set only three things (Security & SD-WAN > Site-to-site VPN): - the mode: hub or spoke; - for a spoke, its hubs; - for each local subnet, whether it is in the VPN (useVpn). The Dashboard then builds tunnels between every spoke and its hubs, and between hubs. Spokes do not build tunnels to each other: traffic from one spoke to another goes through a hub. A subnet that is not in the VPN is not announced to the other sites. In this lab: | MX | Mode | Subnets | |---|---|---| | HUB | hub | 10.9.10.0/24 (in VPN) | | BR1 | spoke of HUB | 10.1.10.0/24 (in VPN), 10.1.20.0/24 (not in VPN) | | BR2 | spoke of HUB | 10.2.10.0/24 (in VPN) | The uplinks reach each other over the router ISP, which knows only the public 203.0.113.x addresses. A host behind an MX can only reach a private address at another site through a tunnel. To change an MX in netverdict, you edit its Dashboard document and import it again in the device inspector, as you would change the setting in the Dashboard. This lab does not change anything: you read and predict.
Topology
8 × router · Cisco IOS-style, cisco-meraki
ISP— routerHUB— routerBR1— routerBR2— routerH-HUB— routerPC-A10— routerPC-A20— routerPC-B10— router
What you will do
On HUB, open the Dashboard view and run
show vpn status. Which peers does the hub have, and which remote subnets does it reach?On BR1, run
show vpn statusandshow route. How does BR1 reach BR2's subnet 10.2.10.0/24?From PC-A10 (10.1.10.10, behind BR1), ping PC-B10 at 10.2.10.10 behind BR2.
From PC-A20 (10.1.20.10, the BR1 subnet that is not in the VPN), ping H-HUB at 10.9.10.10.
Open this lab in your browser →
More labs on this topic
- GRE tunnel: connect two sites over the public internetIntermediate · 18 min
- MPLS L3VPN: connect a customer to a 3rd-party providerAdvanced · 15 min
- MPLS L3VPN — an IOS PE and a Junos PE across a P routerAdvanced · 25 min
- MPLS-VPN — full PE-side configuration (CE has it; now build the PE)Advanced · 18 min
This lab in other languages
Meraki MX — Auto VPN in der Dashboard-Ansicht lesenMeraki MX: leer Auto VPN en la vista del DashboardMeraki MX — ler o Auto VPN na visão do DashboardMeraki MX — lire Auto VPN dans la vue DashboardMeraki MX — Dashboard व्यू में Auto VPN पढ़नाMeraki MX — 在 Dashboard 视图中读懂 Auto VPNMeraki MX — leggere Auto VPN nella vista DashboardMeraki MX — Dashboard ビューで Auto VPN を読むMeraki MX — Dashboard 보기에서 Auto VPN 읽기Meraki MX — читаем Auto VPN в представлении DashboardMeraki MX — Auto VPN'i Dashboard görünümünde okumaMeraki MX — đọc Auto VPN trong chế độ xem Dashboard