Linux Discovery Issue-SNMP probe timed out. Target is either unreachable or there are no valid cred

[mochan_s]

Linux-AIX Discovery
Ran Quick Discovery for one of the passed Test Credential IP which is already present in the IP Affinity List

1. Tried to run the 'Quick' Discovery for this IP.
2. Error="SNMP probe timed out. Target is either unreachable or there are no valid credentials for it."
3. Unix-AIX schedule is also failing.
4. New Linux IP  is giving error.

5. <results error="Adding target to blacklist. No valid credential found for types [SSH Password,SSH Private Key,Azure SSH Certificate]" probe_time="4141" result_code="42">

   <result error="Adding target to blacklist. No valid credential found for types [SSH Password,SSH Private Key,Azure SSH Certificate]">

   <debug_info>
   
   

   {"debug_info":[{"10.55.42.8":{"credentials_attempted":

   [{"credential_type": "SSH Password","credential_name":" AIX ","credential_order":"100","credential_success":false,"credential_id":""},

   {"credential_type": "SSH Password", "credential_name": "Linux", "credential_order":"100","credential_success":false,"credential_id":" "}],"adding_key_to_target_blacklist":true,"connection_parameters":{"credential_types":["SSH Password","SSH Private Key", "Azure SSH Certificate"],"target":"10.55.42.8"}}}]}</debug_info>

[mochan_s]

Hi Pratik,

The IP present in the IP affinity when we are doing 'Test Credential' with this IP it is getting authenticated but when running Quick Discovery it is showing this log in the ECC Queue.This seems very unusual and few times back our schedule was also working but now it is also not working.

[pratik0306 · Accepted solution]

Hi @mochan_s 

If the credential test is success then there must be something wrong with the MID server tagged for it OR the schedule might have any credential alias and it must be picking only that. Can you verify these 2 points.

Also, instead of doing quick discovery can you configure SSH behavior and tag it to the schedule and run the discovery.

[Selva Arun]

Hi,

I see that you have already tested the credentials via instance, could you please log into to your mid servers and run the credential test using an SSH client like PuTTY. For authorization issues, verify command permissions with:.

sudo -l.

Please make sure the User has sudo/ root access in order to successfully scan the device.

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

Selva