discovery againt linux kvm host
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2024 07:50 PM
I am running discovery against Linux KVM hosts. libvirtd is detected but the VM is not. There is no record in cmdb_ci_kvm* table. Please let me know if there are any settings required to detect VMs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2024 08:36 PM
Hi @Yuji ,
Host VM's may not be discoverable due to the following reasons:
1. Discovered VMs doesn't have Public IPs thus no IPs inputted for IP Schedule to scan/discover.
Possible solution: Have the Public IP associated with the VM and ensure they're reachable from the MID via a simple "ping" test.
2. Public IPs are available but not reachable by the MID/MID Cluster selected
Possible solution: Check where the MID is located and if the host is reachable via a simple "ping" test
3. Public IPs available, Host is reachable to VM, but no Credentials available. The discovery status stops at the Classification stage only.
Possible solution: Ensure the credentials are created in the ServiceNow Instance.
4. Public IPs available, Host is reachable to VM, but ports aren't configured properly. The discovery status stops at the Shazzam stage only
Possible solution: Ensure the ports of the hosts are properly configured
5. Public IPs of few are considered but not others during the IP schedule
Possible solution: We do run the IP discovery only on the ACTIVE VMs i.e., Vm's state==on but not on Retired/Terminated VMs so please double-check.
Possible solution: The VM(s) are discovered in the first run and found they're retired in the subsequent runs so IP discovery isn't triggered for those kinds.
Refer : VM Instance and Host VM Discovery
and Linux discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2024 04:27 PM
Hi Sandeep,
Thank you for your response.
I'm looking at this document and it said "The classification triggers the creation of a cmdb_ci_kvm record, and launches the SSH Command probes to explore the Linux server with virsh, lbvert utility, and virtual machine configuration data."
I thought that Discovery would execute VM management commands such as virsh via SSH on the Linux KVM server to obtain VM information, but is this not the case?