Dashboard Throughput, AutoVPN, Default Route

ksumann
Getting noticed

Dashboard Throughput, AutoVPN, Default Route

Hi everyone,

i'm just wondering how dashboard throughput works.

This is from the docs:

ksumann_0-1751965284041.png

 

So for example if you have Auto VPN and a default route, the test just doesn't go through your Uplink, it goes to your Concentrator.
While the actual dashboard communication is always the uplink, ignoring routing settings.

So why does the test test something different?

6 Replies 6
alemabrahao
Kind of a big deal
Kind of a big deal

When you run a throughput test and have Auto VPN set up, the test traffic goes through your VPN concentrator. This checks how well your VPN connection is working.

 

The Meraki Dashboard always talks to your devices through the main internet connection (uplink), no matter what your routing settings are. This ensures reliable management of your network.


So, the test focuses on the VPN path, while the dashboard communication uses the direct internet path.

 

 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
PhilipDAth
Kind of a big deal
Kind of a big deal

I don't believe this is the case, but I can't find a link that states it.

 

I believe that even with a default route in AutoVPN mode, all traffic to the Meraki cloud, including speed test traffic, goes via the local management IP address and the local connection, and not inside the AutoVPN tunnel.  It is a special exception, so that management access to the Meraki device will not be cut off if AutoVPN is down.

ksumann
Getting noticed

Did you try it out?
In our setup, having full tunnel and only specific routes, the throughput test worked fine.

After adding a VPN enabled default route, the test stopped working because its put into the VPN.

PhilipDAth
Kind of a big deal
Kind of a big deal

Here we go:

https://documentation.meraki.com/MX/Site-to-site_VPN/Meraki_Auto_VPN_-_Configuration_and_Troubleshoo...

 

"Note that full-tunneling only affects client data and all Meraki management traffic will egress directly via the primary WAN regardless."

ksumann
Getting noticed

And thats confusing.

There might be cases where the dashboard is not reachable from within AutoVPN, so the test will fail (or showing 0 Mbit) while the device is connected to the dashboard.

Maybe it should allow to select the interface to run the test, ignoring the routes.

cmr
Kind of a big deal
Kind of a big deal

It will time out in that case, I have had it happen a number of times.  I agree it should use the same route as the management traffic.

If my answer solves your problem please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.