Discovery SNMP community credentials are failing

taniabiswas
Kilo Explorer

‎02-19-2019 10:46 PM

Hi All,

I am new to Discovery and facing challenges in executing discovery on a server. I have set the SNMP community credentials for discovery on the instance but those credentials are failing. It says 'Credential test timed out' . It is taking a longer time to test credentials or to test the router access and then it fails. I have set the community rights as read only in the properties of SNMP services and selected accept SNMP packets from any host. Please help me and let me know if I am missing on any step as I am unable to execute discovery because of failing credentials. Any help is much appreciated!. find_real_file.png

Thanks,

Tania

Labels:
Preview file
51 KB
0 Helpfuls
  • 1,619 Views
4 REPLIES 4

robertgeen
Tera Guru

‎02-20-2019 05:34 AM

For the purpose of this I would test by doing a quick discovery on the devices IP and see what comes back in the shazzam probe. Check to make sure it sees SNMP open and it triggers the SNMP probe. At this point if it's doing that you probably need to contact the device owner to get them to whitelist your mid server IP to run SNMP queries on it as 99% of the time that is the problem. If SNMP isn't showing up in the shazzam payload then it's a firewall issue. Thanks.

taniabiswas
Kilo Explorer
In response to robertgeen

‎02-21-2019 10:37 PM

Thanks for your response Robert! I tried the same credentials for a particular IP and port:161 in Kingston version and the credentials got validated but when I am trying these similar steps on a London instance, it says Credentials timed out; is there any other step which I am missing in London version?

0 Helpfuls

John Shores1
ServiceNow Employee
ServiceNow Employee

‎02-20-2019 07:08 AM

taniabiswas, the error you're seeing in the dialog (Credential test timed out) is an access error, not a credential error.  If you have a firewall between your mid server and the host you're trying to discover, you need to make sure SNMP is allowed to cross it. 

taniabiswas
Kilo Explorer
In response to John Shores1

‎02-21-2019 10:38 PM

Thanks for your response John! I tried the same credentials for a particular IP and port:161 in Kingston version and the credentials got validated but when I am trying these similar steps on a London instance, it says Credentials timed out; is there any other step which I am missing in London version?

0 Helpfuls