Unable to get the ESX host and VM's in Vcenter discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2018 08:08 AM
Hello Experts,
I am trying to discovery a vcenter in which I was expecting all the esx host and vm will be automatically discovered.
However it is discovering only the CI where the vcenter app/package is installed/added. Kindly suggest how to get the esxs and vm in that vcenter?
I have checked the vcenter probe result, which is showing all the esx and VM's however not in the devices tab.
Regards,
Sundaresan M

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2018 08:14 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2018 08:18 AM
Hi Sundaresan,
As you expected, ESX should discover automatically while discovering vCenter. however please check below check points.
1. Discovery account should have READONLY access at vCeter level.
2. Please check discovery script Include "VCenterESXHostsSensor" enabled or not.
Note# You can login to vCenter with Discovery account and check if your able to find ESX Servers or not.
This might help...:)
Thanks & Regards,
Vinil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2018 08:32 AM
Definitely check out the above recommendations but for clarification... with our vCenter integration when discovering the vCenter Server/Appliance the only device I see on the Discovery Log tab is the vCenter device itself. However, on the ECC Queue tab I can see multiple triggers for VMWarevCenterVMsProbe, with all the IPs being that of the vCenter device being discovered. Also, when vCenter is discovered it does discover the ESX Servers and it creates/updates the VMware Machine Instance CIs but the actual virtual devices are discovered by the IP assigned to the virtual not during the vCenter discovery.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2018 08:51 AM
Hi Wilson,
When discovering vCenter at IP level, Relationships will create b/w Virtual machines on vCenter and Server table [Windows & linux] that's reason we will see multiple VMWarevCenterVMsProbe on ECC Queue.
Relationship name#" Instantiates - VMware Virtual Machine Instances"
Regards,
Vinil.