Vcenter discovery not updating the ESX servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2024 11:08 AM
Hello everyone,
I'm encountering an issue with the vCenter discovery process. While the VMware vCenter Instances are successfully updating with the latest discovery data, none of the ESX servers are reflecting the most recent discovery date. Although I can see the ESX servers' data in the payload of the VMWarevCenterESXHostsProbe within the discovery queue, the discovery process isn't updating them.
Could someone assist with this? Thanks in advance.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2024 11:35 AM
Servicenow vCenter Discovery | Step by step Discovering VMware using vCenter Discovery.
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2024 11:08 PM
Hi Deepak,
Is it only for ESX server component OR every component of Vcenter discovery?
Is the discovery getting completed without any errors?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2024 12:07 PM
Same issue observing ESX servers not updating while payload on VMWarevCenterESXHostsProbe able to see the data. some where in post processing its not updating records in cmdb. need to check with snow kb article for this issue.