How do I add a Meraki cloud controller?

Deployment considerations

Auvik’s Meraki integration can be configured at the global, multi-site, or individual site level. The appropriate configuration depends on how your Meraki organizations and networks are structured, which collectors can reach those networks, and whether you are using a legacy or newer integration.

Historically, Meraki API requests could be sourced from Auvik’s cloud IP addresses. Newer integrations use an Auvik Collector to source API requests. This allows you to restrict API access to the collector’s public IP address and helps distribute API traffic within Meraki’s rate limits.

For large or multi-site Meraki environments, plan the integration scope before adding credentials.

Add the Meraki API credentials at the highest appropriate level when the same API user and controller scope apply across multiple sites.
Map the appropriate Meraki organizations or networks to the corresponding Auvik sites.
Use a shared collector at the global or multi-site level when the integration is configured there and the collector can reach the required networks.
Configure separate site-level integrations when sites require different collectors, credentials, or network access.
Avoid adding the same Meraki API integration repeatedly across multiple collectors or sites unless separate integrations are required for scope, access, or network reachability.

Changing or deleting a grandfathered Meraki integration may be irreversible. Review the current integration design before making changes.

How to generate an API key

To connect to your cloud controller, you need to generate an API key. The Meraki user generating the key must have access to all organizations that Auvik will manage from the applicable dashboard.

If you have enabled Login IP ranges in the Meraki cloud controller, add the public IP address used by the selected Auvik Collector to the allowed list.

Log in to the Meraki cloud controller web portal.
If your Meraki dashboard contains multiple organizations, select the organization associated with the integration.
From the side navigation, hover over Organization.
Select API Key & Webhooks.
Select the API Keys and Access tab.
Select Generate API key.
Copy and securely store the API key.

How to add API credentials

In Auvik, click Discovery in the side navigation bar.
Click the Manage Credentials tab.
Click the API Credentials tab.
Hover over Add API Credentials.
Choose Meraki.
Enter the following information:
- Credential name
- API key
- Auvik Collector
If no collector is available and you want to map networks at that level, deploy or assign a shared collector with access to the required networks.
Click Test Connection.
Click Save after the connection test succeeds.

If the controller was added from an MSP dashboard, map the Meraki networks to the appropriate Auvik client sites. If it was added from a client dashboard, select the cloud networks that should be managed.

Managing a Meraki controller across multiple sites

When one Meraki dashboard contains networks belonging to multiple Auvik sites, configure the API credentials once at the appropriate scope and map each Meraki network to the correct Auvik site.

Before saving the configuration, confirm:

Each Meraki network is mapped to the intended Auvik site.
The API user has access to all required Meraki organizations and networks.
The selected collector can reach the networks and devices that Auvik must discover.
The collector has the required routing, firewall, and protocol access.
The same Meraki network is not managed by multiple overlapping integrations.

Auvik’s cloud controller configuration adds information about discovered devices. Meraki devices must still be reachable from the collector for proper discovery and management. See How to ensure proper integration and device discovery of Meraki devices.

Changing the collector used by a Meraki integration

You can update the collector associated with a Meraki credential when the integration requires a different network path or collector location.

Go to Discovery > Manage Credentials.
Click Edit next to the Meraki credential.
Select the appropriate Auvik Collector.
Click Test Connection.
If the test succeeds, click Save.

When changing collectors temporarily, confirm the new collector can reach the required Meraki networks and that its public IP address is allowed in Meraki if Login IP ranges are configured.

After the change, allow discovery and inventory data to update, then verify that the correct devices and topology appear under each site. Return the integration to its intended long-term collector configuration when the temporary change is complete.

For primary and standby collector configuration, see Managing multiple collectors.

Avoiding duplicate controllers or devices

Do not configure the same Meraki API credentials multiple times across different collectors or sites unless separate configurations are required.

Duplicate or overlapping configurations can make it difficult to determine which integration or collector is responsible for discovery and may result in duplicate or inconsistent inventory. Before creating another integration, verify whether the existing credential can be mapped to the required sites or networks.

If devices appear under the wrong site or more than once:

Review the Meraki network-to-site mappings.
Confirm the same network is not mapped through multiple integrations.
Confirm collectors do not have overlapping discovery coverage that could place devices in different sites.
Verify routing and reachability from the intended collector.
Allow discovery to update after correcting the configuration.

For shared collector considerations, see How do I manage my shared collector?.

Billing considerations

Multiple Meraki API entries may be billed as multiple controllers. If you are concerned that an integration configuration could affect billing, do not create duplicate integrations as a precaution.

Contact Auvik Support, your Customer Success Manager, or Finance to confirm the recommended configuration and any tenant-specific billing implications.

For general billing criteria, see How does Auvik identify what devices and assets are billable?.

Legacy Meraki integrations

Meraki’s rate limit of 100 calls per second per IP is strictly enforced. Auvik’s centralized cloud API polling model can exceed this limit in large environments. Moving API traffic to on-site collectors distributes the load and can help maintain uninterrupted monitoring.

Customers with large Meraki integrations mapped at the global or multi-site level may need to:

Deploy or select a shared collector at the higher level.
Reconfigure the integration and map networks to the appropriate sites.
Alternatively, configure separate site-level integrations and assign each one to its respective collector.

How can we help?