How to ensure proper integration and device discovery of Meraki devices

To configure Meraki devices at the network-wide level, follow these steps to ensure proper integration and device discovery:

Prerequisites:

Before you begin, make sure:

• You have claimed the devices that you want to add
• You have assigned the devices to the network
• You have set local SNMP credentials for the devices

For instructions on how to do this, review the following Meraki documentation:

• Adding and Removing Devices from Dashboard Networks - Cisco Meraki Documentation
• Using the Cisco Meraki Device Local Status Page

Ensuring Devices Are Reachable (Pingable)

For successful device discovery and integration:

1. Add Routable Networks:

• Navigate to Network-wide > Configure > Addressing & VLANs.
• Ensure that the subnets where devices reside are correctly defined.

2. Enable Scanning:
   • Navigate to Network-wide > Configure > General.
   • Under Device discovery, enable scanning for the relevant networks.
      
3. Verify Connectivity:
   To ensure that the Meraki devices are pingable from the collector.
   Note: This is crucial for devices to be discovered and managed effectively.
    
   • Ensure Routing Between Subnets
     
     If your subnets are on different VLANs, make sure inter-VLAN routing is enabled. Meraki MX and MS devices typically handle this through:
      
     • MX Security Appliance: Use VLANs and set up interface IPs for each VLAN.
     • MS Switches: If acting as Layer 3, define VLAN interfaces and enable routing.
       
       Each subnet must have a route to the collector's subnet.
        
   • Configure Firewall Rules
     
     Check both Layer 3 firewall rules and ACLs (Access Control Lists) to allow ICMP (used by ping).
      
     • On the MX: Go to Security & SD-WAN > Firewall.
     • On MS switches: Use Access Policies or ACLs if configured.
       
       Make sure the firewall rules allow:
       
       ICMP (protocol) FROM: all subnets TO: collector subnet
        
   • Allow ICMP on the Collector
     
     Ensure that the collector itself (OS-level firewall) allows ICMP echo requests from all subnets.
      
   • NAT Considerations
     
     If the subnets are behind different MX appliances or if you're using NAT mode, verify:
      
     • NAT rules are not blocking the ICMP traffic.
     • If the collector is behind an MX, ensure port forwarding or NAT rules (if applicable) allow ICMP.
       • Note: MX devices typically do not NAT traffic between VLANs internally.

• Use Static Routes (if needed)
  
  If the collector is outside the Meraki-managed subnets or in a different site:
   
  • Add a static route in the Meraki dashboard under Security & SD-WAN > Addressing & VLANs > Static routes

• Use Packet Capture or Ping Tool (Meraki)
   
  • Use Tools > Ping in the Meraki Dashboard to test from the MX to the collector.
  • Or use Packet Capture to see if ICMP requests are reaching and replies are returning.

Note: Meraki's API does not automatically discover all devices; they must be reachable (e.g., via ping) for proper integration.

Meraki MX WAN IP is not displayed

Auvik uses information from both the Meraki Dashboard API and device-based SNMP to identify Meraki MX interfaces and WAN information. If the WAN IP is missing, verify that both sources are configured and available.

Verify SNMP

In the Meraki Dashboard:

1. Open the network containing the MX appliance.
2. Go to the network-wide SNMP settings.
3. Confirm that SNMP is enabled.
4. Confirm that the SNMP credentials match those configured in Auvik.
5. Confirm that the Auvik collector can reach the MX management address over UDP 161.

Auvik currently supports device-based Meraki SNMP. See How to enable SNMP on Meraki devices for the supported SNMP configuration.

Verify the Meraki Dashboard API

Confirm that:

• Dashboard API access is enabled in the Meraki organization.
• The API key has read access to the organization and network containing the MX.
• The Auvik Meraki integration is connected and assigned to the correct organization and network.
• The Auvik collector has outbound HTTPS access to the Meraki Dashboard API.
• Any Meraki API allowlist includes the source IP used by the Auvik collector.

Current Meraki API integrations may originate from the Auvik collector rather than from Auvik cloud IP addresses. See How do I add a Meraki cloud controller?.

Confirm the MX WAN uplink is active

In the Meraki Dashboard, confirm that:

• The MX has an active uplink.
• The uplink has a reported public IP address.
• The uplink is assigned to the expected network.
• The MX is not in a pending, disabled, or incomplete configuration state.

Refresh the device information

After correcting SNMP or API configuration:

1. Confirm that the MX is included in the Auvik discovery scope.
2. Rediscover or poll the MX, if that option is available.
3. Allow time for the next polling and integration cycle.
4. Open the device’s Interfaces view and check the WAN or Internet-facing interface.

If the WAN IP is still missing

Check the following:

• SNMP credentials and UDP 161 reachability from the collector.
• API integration status and organization/network mapping.
• Meraki Dashboard API permissions.
• Collector outbound HTTPS access.
• Discovery exclusions or filters that may exclude the MX management IP.
• The MX uplink status and public IP in the Meraki Dashboard.

If the issue continues, provide Support with the Auvik site, MX hostname or serial number, Meraki organization and network, integration status, and the approximate time of the last rediscovery.