VPN Latency in via VPN Status but not via Dashboard API

[Prodrick]

Under what conditions would VPN latency be visible/listed in the Dashboard via VPN Status but not reported via this endpoint:

https://developer.cisco.com/meraki/api-v1/get-organization-appliance-vpn-stats/

For example, in certain customers I am seeing send/receive data via the API and nothing else (like I would expect to see for a non Auto VPN tunnel), but in the Dashboard UI for VPN Status it shows the Latency in ms for the given tunnel.

[Prodrick]

@shwetaP for awareness 😀

[MartinS]

Hi,

Are you talking about this Dashboard latency:

Or this latency dashboard page:

The API call you've mentioned gets stats on the latter, and these Latency, Jitter, Packet Loss and MOS values are there to support the SD-WAN performance based routing functionality and are only collected either if one end of the tunnel has dual uplinks, or you ask support to turn it on if you only have single uplinks. 

[Prodrick]

Hi, @MartinS and thanks for your reply.  I'm familiar with what you're referring to from the documentation, however the customer shared this screenshot (I blurred out their info) where they show the tunnel latency in the Dashboard UI but the API only returns the send/receive data.  I really appreciate you and thanks again.

Below are two screenshots, one from the on-demand Dashboard demo environment and the other from the customer's environment where the latency is shown in the Dashboard UI but not in the API response.

From On Demand DemoActual Customer who reported the issue.

[MartinS · Accepted solution]

Yep, it's frustrating that latency isn't included in an API endpoint (as far as I know), but as I say it is fixable by contacting Meraki support and ask them to enable 'VPN statistics' for the Org

[AnthonyB]

Hi @Prodrick,

The reason you see this in certain customers vs all of them is based on the number of uplinks used by the MX. The probes that we use to gather this data are automatically turned on when there are two uplinks, we use the probing data to make any policy based routing decisions. You can read further about this here - https://documentation.meraki.com/MX/Monitoring_and_Reporting/SD-WAN_Monitoring

In terms of monitoring a single uplink spoke, you are able to see the statistics for a single uplink peer from the hub side if the hub is multi wan enabled. Alternatively as @MartinS has mentioned, there is some back end configuration. However, we encourage you to reach out to your accounts team as there are some design considerations to keep in mind when enabling it.