Meraki MX Appliances

The ThousandEyes - Meraki integration allows users to install ThousandEyes Enterprise Agents on supported Meraki switches, providing better monitoring and testing capabilities for customers interested in improving the quality of their experience and adding the appropriate SD-WAN policies to optimize network performance.

This article provides an overview for the integration and the supported devices.

Use Cases

Meraki Insights (MI) is designed to give Meraki customers an easy way to monitor the performance of web applications and WAN Links on their network and easily identify if any issues are likely being caused by the network (LAN or WAN) or the application server. The data used by MI is based on end-user HTTP/S data that’s already traversing the MX appliance and does not need synthetic probing.

With the ThousandEyes integration, customers can now benefit from enhanced visibility and alerting capabilities by creating customized network and application testing for critical applications inside or outside their infrastructure. For example, a customer can now monitor their internal DNS server response time and availability, as well as measure the average resolution time for a specific domain.

Definitions

  • Tenant: The target domain in the test template.

Supported Devices and System Requirements

Meraki DeviceSupported Test TypesFirmware RequirementsMode
  • MX67

  • MX67W

  • MX67C

  • MX68

  • MX68W

  • MX68CW

  • MX75

  • MX85

  • MX95

  • MX105

  • MX250

  • MX450

All non-browser tests (see Limitations).

MX 18.104 or higher.

NAT Mode is required. Meraki devices running in Concentrator mode are not supported.

Licensing

Meraki Licensing

To take advantage of the ThousandEyes - Meraki integration, you will need:

  • The SD-WAN+ license (for agent installation and test deployment), or

  • The Advanced Security license (for agent installation only)

For more information on Meraki licenses, see Meraki MX Security and SD-WAN Licensing.

ThousandEyes Licensing

The Meraki device will have access to the available units in the ThousandEyes account. See the ThousandEyes Product Description for the terms and conditions applicable to the use of the ThousandEyes platform.

Meraki SDWAN+ customers can claim up to 50 free tests based on their licensing level and supported device count. For more information on how the licenses are calculated, please refer to the Meraki MX ThousandEyes Configuration Guide.

Connectivity

The Meraki device will need to be able to connect to the ThousandEyes platform's cloud infrastructure. For more information, see Firewall Configuration for Enterprise Agents.

In addition to the standard firewall configuration, Meraki devices will need to reach the following cloud endpoint via HTTPS:

  • registry.meraki-applications.com

Installation and Setup

Installation and setup instructions can be found here: Meraki ThousandEyes Configuration Guide.

Limitations

  • Transaction and page load tests are not supported.

  • Using an Enterprise Agent installed on a Meraki device as the target agent of an agent to agent test / RTP test is not supported.

  • vMX is not supported.

  • Meraki EU region’s organization can only be mapped to ThousandEyes EU accounts.

  • All non-EU Meraki organizations can only be linked to ThousandEyes US accounts.

  • Meraki agents use the default uplink interface 0.0.0.0/0 route for connecting to the ThousandEyes platform. For more information on routing policies, see Meraki Routing Behavior.

Account Restrictions

  • ThousandEyes Account Admin users with the local auth permission can link two accounts.

  • Users who have active ThousandEyes user accounts cannot create a new ThousandEyes account as part of the workflow.

  • The Meraki account needs to have at least two administrators.

Disable Forced SSO

ThousandEyes organizations with Forced SSO enabled cannot leverage the Meraki - ThousandEyes integration. To use the integration, Forced SSO must be disabled in the Organization Settings. For more information, see How to Configure SSO: Enabled vs Forced SSO.

Last updated