In discovery, credentials tested successfully, but while triggering the discovery it giving an error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2024 10:33 AM
In discovery, credentials tested successfully, but while triggering the discovery it giving an error invalid credentials.
With the same credentials, I can logged into the server.
In servicenow, credentials tested successfully.
Firewall ports are also open. Ping successfully.
But while triggering the discovery, it is giving an error " Invalid Credentials"
Please assist

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2024 12:00 PM
@Madhura Ambede You can validate the credentials on ECC Queue input of shazam probe.
This way you can be sure which credentials they have used to connect with your server, you will get the sysId of credential on "credential_id" parameter.
May i know what are you trying to discover ?
Let me know if you have any further question for me.
Thanks,
Harsh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-06-2024 11:14 PM
Hello @Harsh Vardhan ,
I am trying for SNMP discovery. As i have checked, there is not in sysID for credentials in ECC queue. Please see attached ECC logs(Shazzam). Please assist.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2024 07:05 AM
@Madhura Ambede I am assuming you are using snmpv3 credentials, Can you try to add below parameter in your mid server ? then restart it and try to do quick discovery again.
mid.snmp.use_snmp_v3
Attempt communication using the SNMPv3 protocol version. Requires configuration of SNMPv3 credentials.
Type: true | false
Default value: true
Doc link :-
Also can you please confirm what sort of network device are you trying to discover ?
Just to add another troubleshoot step, you can try to use Wireshark tool to investigate this issue. Please check the link below.
Thanks,
Harsh