Device credential is failing in Discovery schedule intermittently, even though Credential is correct.

[Oli Sarkar]

Discovery is failing for a IP in discovery schedule. But after discovery schedule is done, If I do quick discovery, CI is getting discovered. In discovery schedule, IP address is added  and creds are also correctly configured. In discovery schedule authentication is failing with error (Adding target to blacklist. No valid credential found for types [SSH Password,SSH Private Key].

We checked the credential being used in schedule which is correct. We checked with Server team logs . In the log we are seeing authentication failure intermittently (not everyday ) . Somedays it's successful , somedays it's failing. Did any else faced the same issue ?

[Mike Toms]

Hi Oli,

The only time I have seen this before is with SMTP and Multiple MID Servers.

Only one of the MID servers was a member of the community so any discovery from the non-member MID Server were failing.

Do you have multiple MID Servers that could be doing the discovery?

If so use the "Test Credential" related link to verify the credential works with each of the MID servers in turn.

If this is a single MID server you may need to check out the MID Server log file "agent0.log.0" for any additional information about a failure.

[Oli Sarkar]

Hi Mike, 

We are using single mid server . And the issue is intermittent. One day it runs fine , after few days suddenly it fails with credential. 

[Mike Toms]

What class of CI are you trying to discover that is causing the problem?

[tim_broberg]

Yeah, SNMP is notoriously finicky.

a) It's UDP.

b) Auth failure manifests as a timeout in the protocol.