Server is getting discovered but VM instance is not getting discovered

Kartikay Nigam
Tera Contributor

‎10-25-2023 05:32 AM

I have some VM in Azure whose server class is getting discovered but its' VM instance is not getting discovered, When the discovery is getting triggered following things are happening-

 

1. In the devices tab of discovery ID 2 records are getting created wherein one says updated and other says active couldn't classify.

KartikayNigam_1-1698236350025.png

 

2. In ECC queue the for the veritas input it says there is no veritas cluster.

KartikayNigam_0-1698236268035.png

 

3. For Unix classify input: 

      VMware, lshmc command not found

 

4.for application dependency mapping input

user  is not allowed to execute '/bin/lsof ' as root

 

How come server class is getting discovered and Virtaul machine class is not getting created. Can someone please explain and help in troubleshooting this

 

 

 

0 Helpfuls
  • 1,030 Views
4 REPLIES 4

Mateus Oliveira
Tera Guru

‎10-25-2023 05:49 AM

Hi @Kartikay Nigam ,

 

I would say that you are discovering this server through Horizontal Discovery and not necessarily Cloud Discovery, which would explain why only the server CI is being created and not the VMI CI.

 

In this other community post (Cloud Discovery vs Horizontal Discovery - ServiceNow Community) you can find details between the two discovery types and documentation references, but in a nutshell, Cloud Discovery what will create the Virtual Machine Instance for your Azure machine and all its relationships to cloud account and other cloud components. On the other hand, if you have only Horizontal Discovery set on IP based Schedules, you will only get the server CI class created.

 

Please, mark my response as helpful in case it helped you. Also mark the question as answered if your questions was solved. This really helps future readers.

Kartikay Nigam
Tera Contributor
In response to Mateus Oliveira

‎10-25-2023 09:17 AM - edited ‎10-25-2023 09:18 AM

Thank you for your time and response So I have created account base discovery, and when I have created a schedule for this cloud account there is one cloud resource discovery schedule which is created and the other VM schedule which is created, so you mean to say that for the discovery which is running for cloud discovery I need to investigate that because in cloud discovery under devices I can see all the regions not any VMs.

0 Helpfuls

Mateus Oliveira
Tera Guru
In response to Kartikay Nigam

‎10-26-2023 02:13 AM

If you are not seeing any VM's whatsoever, I would certainly review the Discovery Schedule for the VM Schedule. Are you getting any error message when this Schedule is triggered? I would also check if the Schedule is properly mapped to the Cloud Service Account in the table cmp_discovery_ldc_config. I have seen some issues with that for Azure Discovery. And it could explain your case, if the servers are being discovered through Horizontal Discovery (IP Based).

 

Please, mar my response as helpful 👍 in case it helped you. And also mark the question as answered in case your issue is solved. This really helps future readers.

Rahul Priyadars
Giga Sage
Giga Sage

‎10-25-2023 09:32 PM

Cloud discovery finds resources in Amazon Web Services (AWS) and Azure clouds, and then populates the CMDB with the relevant CIs and relationships. When you discover a virtual machine in one of these cloud providers, two records are related to that virtual machine. One is called VM Instance, AWS calls it instance and Azure calls it of Virtual machine. The other record corresponds to the guest VM also referred to as Host VM or simply the OS Server. Once a VM Instance is discovered, a record is created in the cmdb_ci_vm_instance table. 

 

Why No VM Instance Discovered- Check required Pattern is Enabled for VM Instance Discovery- Amazon AWS - Virtual Server (LP)

 

Regards

RP

 

 

0 Helpfuls