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.