vCenter Discovery Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2025 12:04 PM
I am trying to discover a vCenter appliance and it just discovers the appliance nothing else. It doesn't launch any other vCenter probes - VMWarevCenterNetworksProbe, VMWarevCenterDatastoresProbe, VMWarevCenterVMsProbe, VMWarevCenterClustersProbe
The credential test is working fine, the credential has been set at Global level and not at the object level.
The url - https://vcenterip/mob opens fine from the MID server using the same set of credentials being used for discovery.
When I checked the Discovery Status > ECC Queue under the HTTPClaissyProbe it has the following payload entries
https://xx.xx.xx.xx:443/api/v1/edge-clusters
<result error="No credential found for type [BASIC_AUTH]" result_code="41">
Similar entries for other end points like /api/cluster, /api/4.0/edges, /net/dns, /mgmt/tm/ltm, /api/json/v2/types, /api/cluster, /api/v1/edge-clusters are also found.
I never had this issue discovering vCenters.
Has anyone seen this before? How did you resolve this?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2025 09:37 AM
Hi @SamJoe,
Can you please check this KB article and let us it is useful or not.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0861899
Thanks
SP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2025 11:59 AM
Hi, looks to be some issue with the user that has a limited visibility over vCenter appliance, please check if "Read-Only" permission is set at the global level there.
