- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2023 06:27 AM
I have an on prem Linux server which was migrated to an Azure Cloud. After the migration, ServiceNow is not able to discover the Linux server on the cloud. ServiceNow successfully discovers the Virtual Machine that it runs on, but it is not discovering the Linux server.
ServiceNow is responding with a credentials issue, but my customer assures me the username and password for discovery is the same as it was on the on prem server.
I'm new to Azure discovery so any help or guidance to resolving this problem is appreciated.
Steve.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2023 07:42 AM
Hi,
Discovering a Linux Server hosted in Azure is actually not Azure Cloud Discovery. It can be triggered from Azure Cloud Discovery if you are able to discover the Virtual Machine but the server discovery is a horizontal host discovery , same as it would be for the on prem environment.
Which means you need to have a MID server with network visibility and credentials to access the server. Some documentation on Linux Discovery can be found here: https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/discovery/referen...
Regards,
Niklas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2023 06:37 AM
Hi @Steve6 sharing this link for your reference https://docs.servicenow.com/en-US/bundle/vancouver-it-operations-management/page/product/discovery/c...
Please mark it helpful if it helps...
Thanks,
Sonia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2023 07:42 AM
Hi,
Discovering a Linux Server hosted in Azure is actually not Azure Cloud Discovery. It can be triggered from Azure Cloud Discovery if you are able to discover the Virtual Machine but the server discovery is a horizontal host discovery , same as it would be for the on prem environment.
Which means you need to have a MID server with network visibility and credentials to access the server. Some documentation on Linux Discovery can be found here: https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/discovery/referen...
Regards,
Niklas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2023 08:17 PM
Login to mid server and check if you can reach to the devices which you want to discover.
Whatever errors you get that solving them will resolve the issue. We recently did lift and shift and it worked. We did not do anything specific.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2023 02:59 PM
Azure Discovery just would add the VM to the Virtual Machine Instance class , if you had ticked (checked) Run VM Based Discovery while you configured the Azure Cloud Schedule another VM Schedule would have triggered automatically , this would try to discover the VM based on horizontal discovery. Please note the pre-requites like ssh (Port 22) and ssh based access / sudoers (if needed) needs to be in place for a successful horizontal linux OS based discovery.