- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 09:08 PM
MY organization recently added several new Linux servers to its infrastructure. These servers are not showing up in the Discovery results. The network administrator has confirmed that the servers are online and accessible. What could be the possible reasons why the new servers are not being discovered, and how would you troubleshoot this issue?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 11:16 PM
This could be because Discovery relies on SSH to connect to Linux servers. If SSH is not enabled or the credentials are incorrect, Discovery will fail.
So check if SSH is enabled on the servers and Verify the SSH port (default is 22) is open and accessible from the MID Server.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI
YouTube: https://www.youtube.com/@learnservicenowwithravi
LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 11:20 PM
Hi @SandeepKSingh ,
There are multiple reason for this, check the below to ensure to see if your discovery works as expected...
1. Go to discovery credentials and check if the creds works as expected. (test the creds).
2. Login to mid server and do a telnet to the target server to see if there is connectivity on port 22.
Command as below:
#telnet <target_server_linux_ipaddress> 22
this must take you to the blank screen which means that port 22 is open from mid server to target IP.
3. Run a quick discovery on 1 IP and check the ECC queue input and output logs to see on which phase the discovery failed.
Based on this further actions can be taken.
Provide me discovery logs to see what can fix the issue or let me know if you see any errors in discovery logs.
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 11:16 PM
This could be because Discovery relies on SSH to connect to Linux servers. If SSH is not enabled or the credentials are incorrect, Discovery will fail.
So check if SSH is enabled on the servers and Verify the SSH port (default is 22) is open and accessible from the MID Server.
If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!
Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI
YouTube: https://www.youtube.com/@learnservicenowwithravi
LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 11:20 PM
Hi @SandeepKSingh ,
There are multiple reason for this, check the below to ensure to see if your discovery works as expected...
1. Go to discovery credentials and check if the creds works as expected. (test the creds).
2. Login to mid server and do a telnet to the target server to see if there is connectivity on port 22.
Command as below:
#telnet <target_server_linux_ipaddress> 22
this must take you to the blank screen which means that port 22 is open from mid server to target IP.
3. Run a quick discovery on 1 IP and check the ECC queue input and output logs to see on which phase the discovery failed.
Based on this further actions can be taken.
Provide me discovery logs to see what can fix the issue or let me know if you see any errors in discovery logs.
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 11:35 PM
Thanks @Ravi Gaurav and @Sohail Khilji ssh port 22 was the issue it was not open. Thanks for quick help