Meraki MV Cameras Are Classified as Generic Devices

Summary

In some environments, Meraki MV cameras (such as MV13 models) may appear in Auvik as Generic devices instead of being properly identified. This typically occurs when Auvik cannot retrieve sufficient device metadata through the Meraki Dashboard API or supporting network discovery data.

Why This Happens

Meraki MV cameras do not provide SNMP data for identification.

Instead, Auvik relies on:

• Meraki Dashboard API integration (primary source of device metadata)
• Neighbor discovery data (e.g., LLDP/CDP) from upstream switches

If the Meraki integration is:

• Misconfigured
• Missing required permissions
• Using an invalid or expired API key

Auvik cannot retrieve model details, and devices may be classified as Generic.

Resolution Checklist

Follow the steps below to restore proper device identification.

1. Confirm Meraki API Access Is Enabled

In the Meraki Dashboard:

1. Navigate to Organization > Settings
2. Ensure Enable access to the API is turned on

2. Regenerate the API Key and Update Auvik

In the Meraki Dashboard:

1. Click your profile (top-right)
2. Go to Profile > API access
3. Generate or regenerate an API key
4. Copy the API key

In Auvik:

1. Navigate to Meraki Integration settings
2. Replace the existing API key with the new one

3. Verify API Permissions and Scope

Ensure the API user has sufficient access:

• Organization-level or network-level read permissions
• Access to the networks containing the cameras

For environments using granular API roles, ensure read access to:

• Organizations
• Networks
• Devices
• Inventory

4. Confirm Organization and Network Alignment

Verify that:

• The MV cameras exist in the same Meraki organization
• The organization and network are included in the Auvik integration scope

5. Trigger a Rediscovery in Auvik

After updating API credentials and permissions:

• Initiate a manual rediscovery in Auvik

This refreshes:

• Device inventory
• Model identification

6. Verify Connectivity to the Meraki API

Ensure outbound connectivity:

• Destination: api.meraki.com
• Protocol: HTTPS (TCP 443)

Check:

• Firewall rules
• Proxy configurations

7. If the Device Still Appears as Generic

If the device continues to appear as Generic after completing the steps above, the issue may be due to missing or incomplete model mapping.

Next Steps

Contact Auvik Support and include the following details:

• Device serial number(s)
• Meraki organization name
• Network name(s)

This information enables Support to validate and update the model mapping where required.

Best Practices

• Keep Meraki firmware up to date
• Ensure LLDP/CDP is enabled on upstream switches
• Regularly validate API key status and permissions
• Avoid overly restrictive API roles unless fully tested