Meraki Quick Start Guide

Edit online

The SevOne Meraki plugin integrates Cisco Meraki cloud-managed networks with SevOne NMS. This integration provides centralized visibility and comprehensive performance monitoring across your wired and wireless infrastructure.

SevOne collects metrics from Meraki devices, including access points (MR), switches (MS), IoT sensors (MT10 and MT14), and SD-WAN appliances (MX). In addition, SevOne can receive IPFIX flows from MX SD-WAN devices. By using this data, you can assess end-to-end network health, streamline troubleshooting with automated workflows, and improve the user experience with cloud-driven intelligence, all within the SevOne NMS platform.

Before you configure the Meraki plugin, complete the following prerequisites:

API Key

An API key is a unique token that authenticates requests to the Meraki Dashboard API. It verifies that the request originates from an authorized user or system. Requests without a valid API key are rejected. For more information about how to generate an API key, see Generate an API Key.

API URI

The API URI is the base endpoint that your application uses to connect to the Meraki Dashboard API. Use the correct URI to ensure that your application connects to the appropriate API environment. The base URI for the Meraki Dashboard API is as follows:

https://api.meraki.com

If your organization is hosted in multiple regions, use the URI that corresponds to your region. For more information, see API Requests.

SNMP credentials

Simple Network Management Protocol (SNMP) credentials are required to monitor and manage MX (SD-WAN), MS (Switches), and MR (Wireless devices). These credentials include the community string or user credentials configured on your devices.

Verify that SNMP is enabled and correctly configured on each Meraki device you want to monitor. Incorrect credentials can cause polling failures or incomplete data collection. For configuration details, see SNMP Overview and Configuration.

Network connectivity

To collect metrics and flow data, SevOne requires connectivity to the Meraki Dashboard API and all Meraki devices in your environment. This connectivity is essential for API communication, ICMP and SNMP polling, and receiving flow data.

The following are the network connectivity requirements for SevOne NMS appliances:

Meraki Dashboard API
HTTPS connectivity is required on TCP port 443 from the NMS peer where the integration is running.
Meraki devices (MX, MR, MS)
  • ICMP connectivity must be allowed for reachability checks.
  • SNMP access must be allowed to support device polling.
Meraki SD-WAN (MX) devices
IPFIX connectivity is required to the relevant SevOne Data Network Collector (DNC).

Organization access

The API key must have permissions to access the organization that contains the devices you want to monitor. If the key is restricted to another organization or lacks privileges, API requests fail.

Verify that your account has the required role and that the API key is associated with the correct organization. For more information about managing organization access, see Managing Dashboard Administrators and Permissions .

What to do next

After you complete the prerequisites, you can configure the Meraki plugin to create integrations and collect metrics for Meraki resources that are associated with your account. For more information about how to configure the Meraki plugin, see Enabling Cisco Meraki Integration.

If you encounter issues during configuration, use the Troubleshooting section to resolve common problems.