Network Discovery

[wendell-gibson]

When running discovery for Meraki devices i keep receiving this same error message "SNMP probe timed out. Target is either unreachable or there are no valid credentials for it."  There are Meraki credentials set up in servicenow but im unsure if they are being properly applied to this discovery schedule or not. Could someone assist?

[Ashok Sasidhara]

Have you checked with network team about whether the 161 port is blocked or if any firewalls are blocking the connectivity from the MID server to the target devices? We had faced a similar issue recently for SNMP discovery which was resolved after getting some connectivity restrictions removed by the network team.

[JessicaLanR]

The error message you're receiving — "SNMP probe timed out. Target is either unreachable or there are no valid credentials for it." — usually points to one of two issues: network connectivity or credential mismatch.

Here are a few steps to help you troubleshoot:

1. Verify Network Reachability
   Confirm that the MID Server can reach the Meraki devices on the network. Try a ping or SNMP walk from the MID Server host to ensure there's no firewall or routing issue.

2. Validate SNMP Credentials
   In Discovery > Credentials > SNMP Credentials, make sure your Meraki SNMP credential is active and scoped properly. It must match the community string or SNMPv3 settings used by the devices.

3. Check IP Ranges and CI Type in Discovery Schedule
   Go to Discovery > Schedules, locate your schedule, and confirm:

   • The correct IP range is targeted.

   • The schedule includes SNMP Classifiers or CI types that match network devices.

4. Use Discovery Debugging Tools
   Try using the Credential Affinity and Discovery Log to see if the Meraki credential is even attempted during the scan. Go to Discovery Status > Devices and check the logs for that IP.

5. SNMP Probe Logs
   Look under Discovery > Discovery Status, drill into the failed device, and open the ECC Queue entries related to SNMP - Classify or SNMP - Collect. That can help pinpoint where the timeout is happening.

If after these steps you're still not seeing success, it's possible the credential isn't being evaluated due to scope or ordering. You can test it directly using the SNMP Credential Test module with the target IP.

Let me know what results you find — happy to help further. If the issue is resolved, don't forget to mark the post as solved for future readers.