AWS EC2 Linux MID Server

H3ll0 Th3r3
Kilo Contributor

Hi Everyone 🙂

I currently have a MID server running on an EC2 Linux instance. It is on a subnet with another dummy EC2 instance for it to discover. I think I have everything properly set up now. The ServiceNow instance seems to be able to detect the dummy EC2 instance through Quick Discover, but I am getting some weird logs. Wondering if anyone knows how to fix these issues.

 

Thanks in advance.

 

find_real_file.png

1 ACCEPTED SOLUTION

DaveHertel
Kilo Sage
Kilo Sage

Hi -- I think your setup is a basic, traditional SN Discovery...   The mention of EC2 and AWS is generating some responses about cloud-stuff that I don't think applies in your scenario.  Since I think you are doing traditional (non-cloud) discovery, it looks like your errors is more basic... i.e. is your MID server installed on Linux?  Are you trying to discover a Windows based machine?  If so, this wont work...

per error:... it implies your MID is Linux based... if so, and you need to discover a WINDOWS machine, this won't work.  To discovery WINDOWS based target devices, you need to use a Windows-based MID server.

find_real_file.png

Does this help?  Hope so

View solution in original post

10 REPLIES 10

Runjay Patel
Giga Sage

Check out this video, it will clear all your doubts and help you to understand Discovery queries in details.

Link: https://www.youtube.com/watch?v=30JbWVsusyE&t=10s&ab_channel=ServiceNowHelpdesk

 

It help you to understand below points.

  • Discovery Overview
  • Discovery prerequisite
  • Understanding Discovery Phases in details
  • Discovery credentials and IP Affinity
  • Mid Server Management with Cluster and Load Balancer
  • Schedule jobs
  • Set up discovery from scratch to end
  • Live implementation with real world data.
  • Troubleshooting on various aspects
  • Many more other issue related to mid server, CIs
  • Cloud discovery
  • Service Mapping

 

Please mark reply as Helpful/Correct, if applicable. Thanks!!