- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2021 11:55 PM
Hi All,
We are discovering some SNMP devices and observed that out of 5 devices 4 are getting discovered finely but the 5th devices throws an error. : SNMP Probe timed out, target is either unreachable or there are no valid credentials for it.
I have observed that for those 4 devices which got discovered: response was received in around 20000 ms but the device which throwing an error says
I got this link below which talks about solution.:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0859825
I currently see no values are set under SNMP - Classify Under Discovery Definition--> probes
Any advise on what value we should be setting up in this fields, as in our case time taken is huge, and also unsure of what value to set, because I can't see the default values in those fields.
Any help will be appreciated.
Regards,
HM
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2021 10:19 AM
I believe the defaults you are looking for are in this document.
https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/r_SNMPProbeParameters.html
Thanks,
Dudley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2024 06:51 PM
Hi @Skinner
I have the parameters on snmp probe form but still facing same issue, can you guide how to change.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2024 05:28 PM
I had the similar issue and got it resolved today. My firewall and crednetials were fine. However, during troubleshooting, I must have set the SNMP credential to apply to a specific MID Server. It was giving this error when the Discovery was running via a different MID Server.
Error: SNMP probe timed out. Target is either unreachable or there are no valid credentials for it.
Solution:
For my situation, I updated the specific credential record (SNMP V3 credential) so that it can be applied to "All MID servers".
I hope this helps.
Regards,
Jude.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2024 08:27 AM
I can't able to see the content in the KB what you have shared.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0859825