Discovery issue "Probe skipped due to failure of previous probe attempt"

shank1
Tera Expert

Hello

I am discovering a IP switch. When I scan it individually, it scans successfully. But that device gets scanned as part of Discovery schedule where some 100 IPs are added in the range, then it says "SNMP probe timed out. Target is either unreachable or there are no valid credentials for it." 

I increased the time out to 10s. Still same issue.

Also in the logs I see this:

find_real_file.png

I see that the device has both ports opened 22, 161. However, based on 161 port opened, it should create the CI.

Why exactly I get "Probe skipped due to failure of previous probe attempt".. How to avoid this.

3 REPLIES 3

Sandeep132
Kilo Sage

Hi Shanks,

First make sure you have SNMP credentials already set up for discovery IP switches. This should avoid the timeout and blacklist errors.

To avoid SSH connections to IP Switch make sure you are using "Use Behavior" for Mid Server selection in the discovery schedule. 

find_real_file.png

And in the behvaior for example "SNMP only" which i created make sure you select the mid server you are trying the connections on and Functaionality definition as "SNMP Only" in the related list. 

find_real_file.png

This should avoid SSH connections to be made. Hope this helps.

Thanks

Hey Sandeep

I know about Behaviors. But that's targeting X device with Y protocol. 

In my case, as valid SNMP credential is there, it should ideally discover the device using SNMP creds.

doug_schulze
ServiceNow Employee
ServiceNow Employee

Just swap the classification priority on the discovery definition > port probes , between ssh and snmp.  With proper access to network devices we will classify with snmp first, never trying ssh.