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 a Meraki API key

The Meraki user generating the key must have access to all organizations and networks that Auvik will manage.

If Login IP ranges are enabled in the Meraki Dashboard, add the public IP address used by the selected Auvik Collector to the allowed list.

Log in to the Meraki Dashboard.
If the 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

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
- Meraki API key
- Auvik Collector
Click Test Connection.
Click Save after the connection test succeeds.

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.

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.

Map organizations and sites

When selecting Meraki organizations or networks in Auvik:

Select only the organizations and networks that should be monitored.
Map each Meraki network to the correct Auvik site.
Confirm that networks are not mapped to multiple Auvik sites.
Verify that the API user can access every organization and network selected for import.

Incorrect mapping can cause devices to appear under the wrong site or prevent the expected devices from being managed.

Configure discovery and reachability

The Meraki integration provides additional information about discovered devices, but Meraki devices must still be reachable from the selected collector for proper discovery and management.

Confirm that:

The subnets where Meraki devices reside are assigned to the correct site.
The required networks are set to Scan under Discovery > Manage Networks.
The collector has routing to the Meraki device subnets.
Firewalls and ACLs allow the required traffic between the collector and the devices.
Meraki devices respond to ping from the collector where required for discovery.

See How to ensure proper integration and device discovery of Meraki devices.

Configure SNMP for additional device metrics

SNMP is optional for the Meraki API integration but may provide additional device-level monitoring data for supported Meraki devices.

In the Meraki Dashboard:

Enable device-based SNMP for the applicable networks.
Select SNMPv2c or SNMPv3 where supported.
Configure the required community string or SNMPv3 credentials.

In Auvik:

Add the matching SNMP credentials at the appropriate site or multi-site level.
Confirm that the collector can reach the Meraki devices using SNMP.
Allow time for the next polling cycle.
Verify that SNMP metrics are populating.

Meraki SNMP support varies by product family. Many Meraki access-point metrics are obtained through the Dashboard API rather than direct SNMP, and some wireless devices provide limited SNMP data.

For SNMP configuration details, see How to enable SNMP on Meraki devices.

Verify the integration

After adding the API key and mapping the networks:

Allow time for the next discovery and polling cycles.
Verify that the expected organizations and networks appear in Auvik.
Confirm that devices are shown under the correct Auvik sites.
Confirm that devices are Managed rather than Unmanaged.
Verify that device details and metrics are populating from the API and, if configured, SNMP.
Review topology and device relationships for accuracy.

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.

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 that:

The new collector can reach the required Meraki networks.
The collector’s public IP address is allowed in Meraki if Login IP ranges are configured.
The selected collector has the required routing, firewall, and protocol access.

After the change, allow discovery and inventory data to update. 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. They may also result in duplicate or inconsistent inventory.

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

Review the Meraki network-to-site mappings.
Confirm that the same network is not mapped through multiple integrations.
Confirm that collectors do not have overlapping discovery coverage.
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?.

Troubleshooting

No organizations or networks appear

Confirm that the Meraki API key is valid.
Confirm that the Meraki user has access to the required organizations and networks.
Test the API connection again in Auvik.
Review any Login IP range restrictions in the Meraki Dashboard.
Confirm that the selected collector’s public IP address is allowed.

Devices appear as Unmanaged

Confirm that the devices are reachable from the selected collector.
Verify that the correct subnets are assigned to the Auvik site.
Confirm that the relevant networks are set to Scan.
If using SNMP, verify that SNMP is enabled and the credentials match in Auvik.
Review integration and discovery logs for authorization or rate-limit errors.

SNMP is not working

Confirm that SNMP is enabled for the applicable Meraki network.
Verify the SNMP version and credentials.
Confirm that the collector can reach the device using SNMP.
Remember that SNMP support varies across Meraki product families and that some metrics are available only through the Dashboard API.

Devices appear under the wrong site

Review the Meraki network-to-site mappings.
Confirm that each network is mapped only once.
Verify that the integration was configured at the intended global, multi-site, or site level.
Allow discovery and inventory data to refresh after correcting the mapping.

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?